[DOCS-11289] Document use of failIndexKeyTooLong parameter during restore Created: 23/Jul/17 Updated: 29/Oct/23 Resolved: 06/Feb/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Nic Cottrell (Personal) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 1 week, 1 day ago |
| Description |
|
Moved to Docs:
Original:
|
| Comments |
| Comment by Githook User [ 06/Feb/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 06/Feb/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 06/Feb/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |
| Comment by David Golden [ 06/Feb/18 ] |
|
LGTM |
| Comment by Kay Kim (Inactive) [ 06/Feb/18 ] |
|
david.golden – let me know if the below is okay: |
| Comment by Kay Kim (Inactive) [ 06/Feb/18 ] |
|
Great. will do. |
| Comment by David Golden [ 06/Feb/18 ] |
|
I think a note on the mongorestore page linking to the failIndexKeyTooLong parameter entry is sufficient. |
| Comment by David Golden [ 23/Jan/18 ] |
|
You'd have to open a SERVER ticket for that. mongorestore sends the index creation command as a batch with all indexes so we don't know which index or document was the problem either. |
| Comment by David Golden [ 11/Oct/17 ] |
|
Updated ticket to indicate that the fix is to document the failIndexKeyTooLong parameter. |
| Comment by William Banfield [ 28/Jul/17 ] |
|
It likely could, but the main priority of the tool is to efficiently load the data into mongodb. It mostly tries to avoid performing operations that should be more carefully considered by a DBA. I'm placing this issue on the backlog while we consider its priority |
| Comment by Nic Cottrell (Personal) [ 27/Jul/17 ] |
|
Thanks - already found failIndexKeyTooLong as a workaround - successfully, but couldn't mongorestore catch this error and continue with the next document in the bson? |
| Comment by William Banfield [ 26/Jul/17 ] |
|
Hey niccottrell, Thanks for opening this issue! The failure you're seeing is from the database. It's failing trying to insert the index document and the tool would not be able to 'force' it in. As a workaround, you can connect to the DB and set failIndexKeyTooLong:false on the destination database. Please follow this ticket as we further consider this feature request. |
| Comment by Nic Cottrell (Personal) [ 23/Jul/17 ] |
|
Maybe --setParameter failIndexKeyTooLong=0 would help? Can this be added to the mongorestore docs? |