[SERVER-73733] Format Ordering in SortedDataInterface for compound wildcard indexes Created: 07/Feb/23 Updated: 29/Oct/23 Resolved: 14/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ruoxin Xu | Assignee: | Ruoxin Xu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | M2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v6.3
|
||||||||
| Sprint: | QO 2023-02-20 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 140 | ||||||||
| Description |
|
Ordering stored in SortedDataInterface/WiredTigerIndex is built from the key pattern object by default. The related code. Wildcard Indexes use a different key pattern than the key pattern stored in the catalog, as a result, the Ordering built for wildcard indexes are incorrect. We should use the format Ordering when we build a SortedDataInterface for WildcardAccessMethod. |
| Comments |
| Comment by Githook User [ 13/Feb/23 ] |
|
Author: {'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}Message: |