-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Storage
-
Fully Compatible
-
Execution Team 2019-06-17, Execution Team 2019-07-01
In 4.2, we removed the index key size limit. It would be confusing to have this server parameter when there is no length limit for the index key. However, we could not remove this server parameter because 4.2 (with FCV 4.0) needs to support this parameter. So we chose to deprecate it in 4.2 and completely ignore it with FCV 4.2.
We should get rid of it in 4.3.
- is depended on by
-
SERVER-41927 Enumerate and remove Execution-related FeatureCompatibilityVersion 4.0-dependent code and tests
- Closed
- is related to
-
SERVER-26786 Calling repairDatabase on collections containing too-long index keys silently drops all indexes on non-MMAPv1 storage engines
- Closed
-
SERVER-36385 Completely remove code and tests about index key size limit
- Closed
- related to
-
SERVER-36329 Deprecate failIndexKeyTooLong server parameter
- Closed