Details
Description
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.
Issue Links
- 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-19281
Add index name as a separate field on duplicate key error object
-
- Open
-
-
SERVER-2633
getLastError and Btree::insert failure
-
- Closed
-
- related to
-
SERVER-12834
Create flag to allow mongod to ignore "index too long" errors
-
- Closed
-
-
SERVER-22078
Consider raising or removing term list length limits for text indexes
-
- Open
-
-
SERVER-5290
fail to insert docs with fields too long to index, and fail to create indexes where doc keys are too big
-
- Closed
-
Activity
Is there some way to figure out how many documents in a collection have keys that will exceed the maximum index size? db.collection.find({$where: "this.something.length > 800"}) is very vague. Do indexes contain the column names, etc...
The indexes doesn't contain the column name. These column names are stored in namespaces.
If this gets implemented, how do we deal with covered index? We'd lose the gain from SERVER-192.
Right now those keys can't be indexed and aren't covered anyway. This is no worse in that case.
The index-spec has the key/field names. The index entries don't store
the field name, it is true.
Will this work with pluggable engines that impose a smaller limit on max key length? For example InnoDB keys must be less than half of a page.
I'd love to see the this increased at a minimum. In my current application where we have to build trees with 1M+ nodes, we leverage the materialized path approach and even with using short descriptors we are limited to a tree depth of ~75. We are already approaching 60 levels deep in the tree. This limit is causing us to have to consider a different vendor because in the near future our application will just not work b/c of this limit.
Has there been any movement on this issue? I am really in a tight spot. In our application there are millions of nodes in the tree and querying the tree and subtrees fast is critical. We also perform billions of db transactions on the tree and we have just found the materialized path approach to be the best mechanism for our needs. Is it possible to at least increase the allowed length? Even just doubling the allowed key length would help us immensely.
would need to point to start of the document in the collection rather than its exact position as exact field positions move over time when updated