[SERVER-55681] Collections clustered by _id need to reject duplicate _id values Created: 31/Mar/21  Updated: 29/Oct/23  Resolved: 07/Apr/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-55342 WiredTigerSession::CursorCache should... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2021-04-19
Participants:

 Description   

Inserts into WiredTigerRecordStore set the "overwrite" cursor flag to true in all cases.

Regular collections with a separate _id index reject duplicate _id values by setting the "overwrite" flag to false.

This is likely not problematic for time-series collections because they use ObjectId, but collisions are possible.

For clustered collections only, set the "overwrite" flag to false.



 Comments   
Comment by Githook User [ 08/Apr/21 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-55681 Prevent clustered_index_types.jsfrom running in parallel suite on
ephemeralForTest
Branch: master
https://github.com/mongodb/mongo/commit/24816f527630968a5047c5f9ab73c793b5b7d5a9

Comment by Githook User [ 07/Apr/21 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-55681 Clustered collections should reject duplicate _id values

The WiredTigerSessionCache should not mix cursors with different
overwrite settings.
Branch: master
https://github.com/mongodb/mongo/commit/4a3fb620ac72e380c42e215c74045bee60e16066

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