[SERVER-9447] Key values too large to index Created: 24/Apr/13  Updated: 10/Dec/14  Resolved: 25/Apr/13

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

Type: Question Priority: Minor - P4
Reporter: Joseph Laptavijok Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS 5.9


Issue Links:
Duplicate
duplicates SERVER-5290 fail to insert docs with fields too l... Closed
Participants:

 Description   

A few questions regarding key values too large to index. What happens to a key value is too large to index? In particular, what happens to that entry? Is it indexed up to the full 1024 byte limit? Is it skipped?

Also what happens during querying? If an value is not in the index because it is too large, will MongoDB do a full table scan for that value? Or will MongoDB only return values that are indexed?

Thanks for answer my many questions.



 Comments   
Comment by Joseph Laptavijok [ 25/Apr/13 ]

Thank you for the info Dan.

Comment by Daniel Pasette (Inactive) [ 25/Apr/13 ]

Hi Joseph, please see this ticket for more information: SERVER-5290.

At this time, the behavior is that the document is inserted, but an index entry on a field greater than max size is not created. If the query optimizer chooses an index to use where this has occurred, the document will not be retrieved and no additional table scan will be performed. This bug is scheduled to be fixed in the 2.5 development cycle.

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