[SERVER-67071] Sharding should not use hidden indexes Created: 07/Jun/22 Updated: 28/Sep/22 Resolved: 28/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Renato Riccio | Assignee: | Garaudy Etienne |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sharding-product-sync | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
MongoDB 4.4 introduces the possibility to hide an index, this allows to ensure that there are no performance impact on dropping it.
|
| Comments |
| Comment by Garaudy Etienne [ 12/Aug/22 ] |
|
The conclusion here is that if you cannot drop a shard key index, then you should not be able to hide that index. As such, I will create a query ticket to add that limitation to hidden indexes. |
| Comment by Garaudy Etienne [ 15/Jul/22 ] |
|
No we haven't. Adding to agenda. |
| Comment by Lamont Nelson [ 15/Jul/22 ] |
|
garaudy.etienne@mongodb.com ping. Did we get to this one in the product sync? |