[DOCS-13782] [TOOLS] mongorestore option creates a collection with a new UUID if no UUID is found for it Created: 22/Jul/20  Updated: 05/Feb/24  Due: 24/Jul/20  Resolved: 01/Feb/24

Status: Closed
Project: Documentation
Component/s: tools
Affects Version/s: None
Fix Version/s: Server_Docs_[20240205]

Type: Task Priority: Major - P3
Reporter: Anonymous Assignee: Lauren Tran
Resolution: Won't Do Votes: 0
Labels: backlog, feature, quick-win, server-docs-bug-bash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents TOOLS-2531 mongorestore hung if restoring views ... Closed
Participants:
Days since reply: 6 days ago
Story Points: 1

 Description   

Description

from Tim: add to mongorestore --preserveUUID docs that mongorestore will create a collection with a new UUID if no UUID is found for it in the dump.

 

 

 

Engineering Description
When restoring database views by using mongorestore command with `--preserveUUID --drop` options, mongorestore command hangs.

+ mongo --quiet --eval 'db.version()'
4.2.3
+ mongo --quiet --eval 'db.createView("view", "coll",   [ { $project: {"field1": 1 } } ] )' test
{ "ok" : 1 }
+ mongodump --archive
2020-03-24T14:52:05.833+0300	writing admin.system.version to archive on stdout
2020-03-24T14:52:05.836+0300	done dumping admin.system.version (1 document)
2020-03-24T14:52:05.836+0300	writing test.view to archive on stdout
2020-03-24T14:52:05.838+0300	done dumping test.view (0 documents)
+ cat dump
+ mongorestore --archive --drop --preserveUUID
2020-03-24T14:52:05.898+0300	preparing collections to restore from
2020-03-24T14:52:05.922+0300	reading metadata for test.view from archive on stdin
2020-03-24T14:52:05.923+0300	finished restoring test.view (0 documents, 0 failures)
...hung here...

The version for both mongod and mongorestore is 4.2.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Lauren Tran [ 01/Feb/24 ]

Closing this ticket after concluding with tim.fogarty@mongodb.com that this change is not necessary

Comment by Tim Fogarty [ 31/Jan/24 ]

Oh I see there's already a PR for it though. I do think the PR text looks correct so we could add it if we want.

Comment by Tim Fogarty [ 31/Jan/24 ]

I had another look at this and honestly I don't think we need to do this. I think the current documentation is sufficient. There's no need for this extra detail.

Comment by Sarah Olson [ 17/Aug/22 ]

Hi tim.fogarty@mongodb.com. Can you help me with priority for this ticket? I am going to revert to unassigned, and this ticket will live in our Server docs team backlog. Someone will pick it up as time allows. If you think it needs higher priority than this, please let me know and we'll get it assigned to someone accordingly.

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