-
Type:
New Feature
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 2.5.4
-
Component/s: Index Maintenance
-
None
-
Fully Compatible
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
In SERVER-5290, mongod correctly returns an error when trying to index a key over the maximum allowed length. There are plenty of workarounds for new applications (hash the value, truncate the value), but for existing applications with millions of documents, this causes major issues.
Allowing users to relax this restriction will permit them to gradually deal with these bad index entries. They can use the upgradeCheck tool (SERVER-8391) provided in 2.6 to get an idea if this is something they need or not.
To enable this flag starting in 2.6.0, start mongod with --setParameter failIndexKeyTooLong=0. It defaults to true.
- is duplicated by
-
SERVER-30188 Index option to skip keys that are too large
-
- Closed
-
- is related to
-
SERVER-3372 Allow indexing fields of arbitrary length
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-12982 Could not restore backup data due to "key too large to index"
-
- Closed
-
-
-
- Closed
-