-
Type: Bug
-
Status: Resolved
-
Priority: Critical
-
Resolution: Fixed
-
Affects Version/s: 10.10
-
Fix Version/s: 9.10-HF41, 10.10-HF21, 11.1, 2021.0
-
Component/s: Core MongoDB
-
Release Notes Summary:Nuxeo handles possible duplicates creation in MongoDB.
-
Release Notes Description:
-
Epic Link:
-
Tags:
-
Backlog priority:900
-
Sprint:nxplatform 11.1.25, nxplatform 11.1.26
-
Story Points:5
Concurrent threads can currently create documents with the same parentId and the same name => both documents will appear in the UI but it will be possible to navigate to only one using the path.
There should be a check in Nuxeo code to avoid these duplicates, in MongoDBRepository.createState where a comment indicates that dupes should be handled.
db.collection.createIndex( { "ecm:name": 1, "ecm:parentId": 1 }, { unique: true } )
Note that this doesn't work with sharding so this should be optional.
- causes
-
NXP-28527 Fix TestMongoDBIndices.shouldFailWhenCreatingExistingChildNameDocument on mongodb4
- Resolved
- is related to
-
NXP-22421 Database-level integrity constraints for PostgreSQL
- Resolved
-
NXP-28495 Fix possible bug in Document Import with slow server responses
- Resolved
-
NXP-27654 Add a unique index on ecm:id in MongoDB
- Resolved
- Is referenced in