[SERVER-53997] Ban use of indexes excluded from API verison 1 for query planning when apiStrict set to true Created: 22/Jan/21 Updated: 29/Oct/23 Resolved: 01/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ruoxin Xu | Assignee: | Ruoxin Xu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Query 2021-02-08 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The query commands (like find, aggregate) will not consider these "unstable" indexes for planning if apiStrict is set to true. Currently "geoHaystack" and "text" indexes are excluded from API version 1. |
| Comments |
| Comment by Githook User [ 30/Jan/21 ] |
|
Author: {'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}Message: |
| Comment by David Storch [ 25/Jan/21 ] |
|
Got it, thanks. |
| Comment by Ruoxin Xu [ 25/Jan/21 ] |
|
david.storch Yeah, "geoHaystack" and "text" indexes are excluded from API version 1. As designed these indexes cannot be created or used for planning with "APIStrict: true" in API version1. |
| Comment by David Storch [ 25/Jan/21 ] |
|
ruoxin.xu what is an "unstable index"? Are there kinds of indexes that are excluded from API Version 1? |