- 
    Type:Improvement 
- 
    Resolution: Duplicate
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: None
- 
    Component/s: Index Maintenance, MMAPv1
- 
    None
- 
        Storage NYC 2018-08-27
- 
        (copied to CRM)
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
The current index format has a maximum key length limitation and starting in 2.6, prevents inserting new documents that contain indexed fields exceeding this length.
- duplicates
- 
                    SERVER-36278 Remove the 1KB index key size limit -         
- Closed
 
-         
- is duplicated by
- 
                    SERVER-10749 Query results differ depending on the utilized index -         
- Closed
 
-         
- 
                    SERVER-6417 duplicate _ids possible when values exceed max index key size -         
- Closed
 
-         
- 
                    SERVER-7638 explain() returns different results than count() when using hint() -         
- Closed
 
-         
- is related to
- 
                    SERVER-14791 Mongorestore error recreating index causes entire restore failure -         
- Closed
 
-         
- 
                    SERVER-2633 getLastError and Btree::insert failure -         
- Closed
 
-         
- 
                    SERVER-19281 Add index name as a separate field on duplicate key error object -         
- Closed
 
-         
- 
                    SERVER-30188 Index option to skip keys that are too large -         
- Closed
 
-         
- related to
- 
                    SERVER-12834 Create flag to allow mongod to ignore "index too long" errors -         
- Closed
 
-         
- 
                    SERVER-22078 Remove term list limits for text index in FCV 4.2 -         
- Closed
 
-         
- 
                    SERVER-5290 fail to insert docs with fields too long to index, and fail to create indexes where doc keys are too big -         
- Closed
 
-