Skip to content

Index intersection and sort #2776

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

Open
wants to merge 1 commit into
base: v3.2
Choose a base branch
from
Open

Conversation

fmestrone
Copy link

@fmestrone fmestrone commented Nov 22, 2016

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 Reviewable

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?
Copy link

@bukkasamudram bukkasamudram left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants