[DOCS-8702] Incorrect example of query to show Index Intersection Mechanism Created: 30/Aug/16  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Dmytro Drachov Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

official docker image, mongo:3.0.2

Location: https://docs.mongodb.com/v3.0/core/index-intersection/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
Referrer: https://docs.mongodb.com/v3.0/core/indexes-introduction/
Screen Resolution: 1440 x 900


Issue Links:
Related
related to DOCS-9723 Use another query to trigger index in... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

From documentation
...
MongoDB can use the intersection of the two indexes to support the following query:

db.orders.find( { item: "abc123", qty:

{ $gt: 15 }

} )
...

Based on that improvement and comment intersection should not work with range query. So the example should be like db.orders.find( { item: "abc123", qty:

{ $eq: 15 }

} )



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:56:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.