[SERVER-29272] Two Phase Drops: listCollections should exclude drop-pending collections Created: 18/May/17 Updated: 30/Oct/23 Resolved: 06/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Repl 2017-05-29, Repl 2017-06-19 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
Collections will no longer be dropped immediately with 2-phase drops (still in progress). Instead, the collections that the user requests to be dropped will be renamed to a non-user visible collection in the same database in the <db>.system.drop.* namespace (see Currently the listCollections command should be excluding drop-pending collections from its results. If the user wants to see these hidden collections, there should be an option to listCollections to include these drop-pending collections. |
| Comments |
| Comment by Benety Goh [ 06/Jun/17 ] |
|
The work to extend listCollections to support listing drop-pending collections has been moved to |
| Comment by Eric Milkie [ 01/Jun/17 ] |
|
Unfortunately, the commit above is already in 3.5.8, and any further commits will go in 3.5.9. Shall we break this ticket up into two pieces? The work still be completed is to add an option to the listCollections command so that it does not hide drop-pending collections. |
| Comment by Githook User [ 25/May/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |