Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leverage search method when working with single orderBy parameter #5

Open
timmixell opened this issue Oct 8, 2020 · 0 comments
Open
Assignees

Comments

@timmixell
Copy link
Contributor

The executeSelect method currently always routes searches through the aggregation interface. This requires a call to get a list of IDs that satisfy the search criteria, and subsequently a call to retrieve the documents associated with those IDs. This is done to accommodate the potential for multiple SORT BY criteria.

In the scenario where a single sort field is furnished, a single search call may be made to retrieve all matching documents in a single call.

@timmixell timmixell self-assigned this Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant