Index intersection and sort #2776
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I cannot follow the document as it is, so I wonder whether there was a mistake in it. You say that query intersection cannot be used for the query, and that individual indexes will also not be used. In other words, can the query not be optimised at all? That sounds unlikely. Did you mean what I am suggesting here?
bukkasamudram
left a comment
bukkasamudram
left a comment
There was a problem hiding this comment.
Hello,
I agree with @fmestrone,
Hopefully, winning plan should be using single filed index on qty field. Rejected plans may include other indexes.
mongo-cr-bot
pushed a commit
that referenced
this pull request
Mar 27, 2023
* DOCSP-27508 Updates mongodump and mongorestore examples * Fixes build issue * Fixes build issue * Fixes build errors * Fixes build issue * Fixes build issue * Fixes per Jeff * Fixes per Dave
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I cannot follow the document as it is, so I wonder whether there was a mistake in it. You say that query intersection cannot be used for the query, and that individual indexes will also not be used. In other words, can the query not be optimised at all? That sounds unlikely. Did you mean what I am suggesting here?
This change is