[SERVER-60734] Replacement updates should preserve the cluster key Created: 15/Oct/21 Updated: 03/Jan/23 Resolved: 03/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Josef Ahmad | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | clustered_collections | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Replacement updates on clustered collections currently assume _id as the cluster key. Extend the logic to support arbitrary cluster keys. |
| Comments |
| Comment by Connie Chen [ 03/Jan/23 ] |
|
Closing as won't do as we believe we'll be moving away from clustered collections |