[SERVER-61980] collMod does not consider unique option in no-op hidden parameter request processing Created: 10/Dec/21  Updated: 29/Oct/23  Resolved: 10/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:
Related
related to SERVER-62000 Do not generate "unique" field in opl... Closed
is related to SERVER-48047 Do not generate "hidden" field in opl... Closed
is related to SERVER-61158 Convert a non-unique index to a uniqu... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2021-12-13
Participants:

 Comments   
Comment by Githook User [ 15/Dec/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-61980 migrate ParsedCollModIndexRequest::indexUnique away from BSONElement
Branch: master
https://github.com/mongodb/mongo/commit/46dff5cfba21cd1692c600a312904afa9cd71e43

(incorrectly committed under this ticket. should be SERVER-62000)

Comment by Githook User [ 10/Dec/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-61980 validate collMod unique index option before processing no-op hidden parameter
Branch: master
https://github.com/mongodb/mongo/commit/207641bc5bf091a7e910ba88e12e1b1eff49874d

Comment by Githook User [ 10/Dec/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-61980 ensure oplog contains "unique" if collMod "hidden" parameter is a no-op
Branch: master
https://github.com/mongodb/mongo/commit/b21857a79339e21c9452a2d85c4fa2c25e0cb451

Comment by Benety Goh [ 10/Dec/21 ]

The collMod request parsing logic emits a sub-document for the index field when the hidden index option matches the current setting in the catalog. It currently takes the TTL option into account, but not the new unique option.

See SERVER-48047 and SERVER-61158.

Generated at Thu Feb 08 05:53:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.