[DOCS-8542] Index Intersection page does not mention TEXT, 2d or 2dsphere indexes Created: 10/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: | Task | Priority: | Major - P3 |
| Reporter: | William Byrne III | Assignee: | Andrew Aldridge |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All post version 2.6 |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
|
Our Index Intersection page (https://docs.mongodb.com/manual/core/index-intersection/) makes no mention of text, 2d or 2dsphere indexes. I'm pretty sure that those indexes can't participate in index intersection because they are quite different from BTree indexes and are used via type specific functions like $text and $near. I wanted to point the user to a manual page that said that definitively, but there is no such place. Another place this could be mentioned is on the 2dsphere and text indexes pages: |
| 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! |
| Comment by William Byrne III [ 19/Aug/16 ] |
|
This has been clarified in the Help ticket by Tess Avitabile tess.avitabile : Text indexes do not participate in index intersection. 2d and 2dsphere indexes can participate in index intersection, though as you said, not with $near. They can participate for a $geoWithin query. For example, if you have indexes {a: 1} and {b: '2dsphere'} (or {b: '2d'}), you can have index intersection for the query {a: 1, b: {$geoWithin: {$centerSphere: [[0, 0], 1]}}}. |