[SERVER-79358] Dropping a collection in a replicaset should result in a no-op for 6.0 and below Created: 26/Jul/23 Updated: 27/Jul/23 Resolved: 27/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.19, 6.0.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Enrico Golfieri | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
After However for a replica-set this is not the case for 6.0 and below. Since we want to keep the user experience as uniform as possible, dropping a collection in replica-set should behave the same.
Currently on a sharded sharded cluster on 6.0 }, , } Currently on a replica-set in 6.0 }, |
| Comments |
| Comment by Enrico Golfieri [ 27/Jul/23 ] |
|
After talking with max.hirschhorn@mongodb.com we opted for discarding this ticket. Having a command stop returning an error in a minor version upgrade seems it wouldn't actually effect the downstream users both internally and externally |
| Comment by Enrico Golfieri [ 26/Jul/23 ] |
|
max.hirschhorn@mongodb.com we are currently back-porting an inconsistency in the errors reported by the renameCollection (BACKPORT-16594). This ticket is the result of this discussion It's only about keeping the user experience as uniform as possible. If we shouldn't backport this ticket to 6.0 then also BACKPORT-16594 should not be merged |
| Comment by Max Hirschhorn [ 26/Jul/23 ] |
|
I'm not sure we should change the behavior of existing commands in a stable release branch. enrico.golfieri@mongodb.com what motivated this request? |