[SERVER-15121] limit scope of iterator in renameCollection command Created: 03/Sep/14  Updated: 08/Sep/14  Resolved: 04/Sep/14

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.7.5
Fix Version/s: 2.7.6

Type: Improvement Priority: Major - P3
Reporter: Michael Cahill Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: community-team, pull-request
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
Sprint: Server 2.7.6
Participants:

 Description   

WiredTiger checks for open cursors during drop and rename operations. This causes problems in the rename7.js test, which renames a collection between databases. That is implemented as a loop that copies the records followed by a drop. The problem for WiredTiger is that the iterator used for the copy isn't closed before drop.



 Comments   
Comment by Githook User [ 04/Sep/14 ]

Author:

{u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@wiredtiger.com'}

Message: SERVER-15121 When doing renameCollection across databases, close the iterator used for the copy before dropping the source collection.

Closes #763

Signed-off-by: Benety Goh <benety@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/5c7bc01c21eca31946f476c22e83714f74e4c375

Comment by Ramon Fernandez Marina [ 03/Sep/14 ]

Thanks for your report mjc@wiredtiger.com. For the record the pull request is here.

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