[SERVER-48626] Inserting duplicate entries in unique indexes with the CollectionBulkLoader leads to entries not being indexed with the biggie storage engine Created: 05/Jun/20 Updated: 29/Oct/23 Resolved: 23/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Henrik Edin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution Team 2020-06-15, Execution Team 2020-06-29 | ||||
| Participants: | |||||
| Linked BF Score: | 10 | ||||
| Description |
|
This unittest exposes the issue when run over biggie: https://github.com/mongodb/mongo/blob/cbf2cb2cd7288b6b0aae866296d2c1f1acd344ad/src/mongo/db/repl/storage_interface_impl_test.cpp#L560-L582 |
| Comments |
| Comment by Githook User [ 23/Jun/20 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: Unique indexes now have a binary representation that allowes for duplicates, and there's no fallback to embedding the record id in the keys that causes issues. Unique and standard indexes have separate formats, similar to WT. |