[SERVER-36386] Remove failIndexKeyTooLong server parameter Created: 31/Jul/18  Updated: 29/Oct/23  Resolved: 24/Jun/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.14

Type: Task Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Gabriel Villasana (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng, nyc, open_todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-41927 Enumerate and remove Execution-relate... Closed
Documented
Related
related to SERVER-36329 Deprecate failIndexKeyTooLong server ... Closed
is related to SERVER-26786 Calling repairDatabase on collections... Closed
is related to SERVER-36385 Completely remove code and tests abou... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-06-17, Execution Team 2019-07-01
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 24/Jun/19 ]

Author:

{'name': 'Gabe Villasana', 'username': 'villagab4', 'email': 'villagab4@gmail.com'}

Message: SERVER-36386 Remove failIndexKeyTooLong server parameter
Branch: master
https://github.com/mongodb/mongo/commit/3bf10866faf60721d75aa78f6ea1df88f838fd52

Generated at Thu Feb 08 04:42:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.