[DOCS-13800] [TOOLS] Check for duplicate index keys after converting legacy index definitions Created: 29/Jul/20  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: tools
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Anonymous Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents TOOLS-2645 Check for duplicate index keys after ... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-11348

 Description   

Description

Engineering Description
If a dump has two indexes, {foo: ""} and {foo: 1}, and we restore with --convertLegacyIndexes, then we will get an error: 

(IndexOptionsConflict) Index with name: foo_1 already exists with a different name

We could check to see if we have duplicate indexes after legacy index conversion and discard the legacy index, or we could just ignore the error.

Both options would have the effect of removing the legacy index. This would mean that index hints for that index would no longer work in the restored db.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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