[SERVER-62000] Do not generate "unique" field in oplog if collMod "unique" parameter is a no-op Created: 13/Dec/21 Updated: 29/Oct/23 Resolved: 15/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| 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 | ||||||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||||||
| Sprint: | Execution Team 2021-12-13, Execution Team 2021-12-27 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
If we use the collMod "unique" parameter, which currently has to be set to true, on a index that is already unique, the primary still generates the following oplog entry that will cause oplog application on a secondary to fail:
For a no-op "unique" collMod request, we should apply a strategy similar to that implemented in This is follow-up work to This applies to a flag-guarded feature that is still under development. |
| Comments |
| Comment by Benety Goh [ 15/Dec/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (incorrectly committed under |
| Comment by Githook User [ 15/Dec/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 15/Dec/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 15/Dec/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |