[SERVER-71252] Ensure API consumer can get global indexes separately from regular indexes Created: 10/Nov/22 Updated: 29/Oct/23 Resolved: 10/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2583-Milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23 |
| Participants: |
| Description |
|
Currently there is no separation in the CSR nor the CatalogCache API between global and non-global indexes. However, it is required that we provide consumers a way to query the existence of only global indexes. In order to determine if an index is global or not, there should be a 'global: true' field in the options object. We could add to the currently implemented cache functions to allow iterating over or query for regular, global or all indexes. |
| Comments |
| Comment by Githook User [ 10/Jan/23 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |