[SERVER-33153] Include collection and index in "key too large to index" errors Created: 07/Feb/18  Updated: 06/Dec/22  Resolved: 22/Jun/18

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

Type: Improvement Priority: Minor - P4
Reporter: David Bartley Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-14543 Display _id of document that fails in... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

"Key too large to index" errors don't include either collection or index in their text, so it's difficult to determine which index is problematic. For comparison, "duplicate key" errors include collection and index.

It looks like the mmvap1 implementation at least index.



 Comments   
Comment by Ian Whalen (Inactive) [ 22/Jun/18 ]

Closing as Won't Fix since we're removing the limitation on index entry size in 4.2.

Comment by Kelsey Schubert [ 25/Apr/18 ]

Hi bartle,

Sorry for the delay getting back to you – I've reopened the ticket. It looks like you've already signed the contributor agreement so if you'd like to open a pull request for this improvement, someone from the storage team will review it.

Thank you,
Kelsey

Comment by David Bartley [ 12/Feb/18 ]

That other bug suggests that it would be hard to thread _id through to the error message, so seems less likely to be fixed in the short term. Given that the original bug here would require a simple ~5 line change (which I'm happy to provide), would it make sense to leave it open?

Comment by Mark Agarunov [ 09/Feb/18 ]

Hello bartle,

Thank you for the the report. Looking over your description of the desired behavior of show the keys that are too long for the index, I believe this is the same behavior detailed in SERVER-14543 so I've closed this ticket as a duplicate. Please watch SERVER-14543 for updates on this issue.

Thanks,
Mark

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