----------------------------

Original Description

Description:

Remove documentation on any index name limit mention.

Engineering Ticket Description:

As described in https://docs.mongodb.com/v3.4/reference/limits/#indexes, mongod inforces a limits of 128 characters for the combination of index_name and database_name when creating indexes. (Similar restrictions apply to collection names for the creation of collections.)

This can cause errors when unloading / reloading data (e.g., with mongodump and mongorestore) to create test environments in which the database names may differ from the original source.

For example, when unloading data/indexes from a production database named abc and loading into a database named abc-uat-2018jan29 for testing purposes, index names that had been legal in the source database may no longer be legal in the destination database.

Although this can be resolved by renaming indexes, doing so violates testing protocols, as hinted queries will no longer function equivalently (without change) in both environments.

To overcome this, it would be helpful if separate and independent limits were enforced on database names and on index / collection names; this would ensure that any collection or indexe that can be successfully created in one database can be exported and imported into any other database.

----------------------------

Description

Scope of changes (files that need work and how much)

*only if fcv = 4.2*

• Update limits and modify references
• 4.2 release notes and compatibility (fcv section)
• 4.2 downgrade prereq

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)