[SERVER-58906] Remove last-lts check for renameCollection in commands_that_write_accept_wc_shards.js Created: 28/Jul/21 Updated: 29/Oct/23 Resolved: 04/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.1.0 |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding EMEA 2021-08-09 | ||||||||
| Participants: | |||||||||
| Description |
|
This check was added when the last-lts version was v4.4 and invalid write concerns passed to renameCollection were expected to trigger a write concern error. Starting from v5.0, no write concerns is propagated anymore for renameCollection as the majority write concern is applied by default. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 04/Aug/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Tommaso Tocci [ 03/Aug/21 ] |
|
pierlauro.sciarelli I think you forgot to remove the disabled_due_to_server_58295 from the test |
| Comment by Githook User [ 28/Jul/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |