[SERVER-29373] Two Phase Drops: Relax index namespace length constraint under non-mmapv1 storage engines when doing collection renames for two phase drops - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.5.10
Component/s: Storage, WiredTiger
Labels:
None

Backwards Compatibility:
Minor Change
Sprint:
Repl 2017-07-31

Description

Under MMAP, there's a limit on the generated index namespace in a collection due to the on-disk format. This constraint imposes a restriction on the target collection namespace when we are doing collection renames. It's likely that this constraint may not apply to WiredTiger.

This may have implications for importing databases between different storage engines and also for downgrade to previous versions of the server that still have this restriction.

Attachments

Issue Links

is related to

SERVER-7720 Building an index with a too-long name should always fail

Closed

SERVER-29274 Two Phase Drops: rename collection to special drop-pending name

Closed

SERVER-29747 Two phase drops: drop indexes before renaming collections if the rename will make the index name too long

Closed

related to

SERVER-29747 Two phase drops: drop indexes before renaming collections if the rename will make the index name too long

Closed

Activity

People

Assignee:: Benety Goh

Reporter:: Benety Goh

Participants:: Benety Goh, Eric Milkie, Geert Bosch, Githook User, Spencer Brody

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: May 25 2017 05:14:29 PM UTC

Updated:: Oct 12 2017 08:58:27 PM UTC

Resolved:: Jul 12 2017 11:09:22 PM UTC