[SERVER-11418] cloneCollection ignores the copyindexes field Created: 28/Oct/13 Updated: 06/Dec/22 Resolved: 05/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.2.6, 2.4.7, 2.5.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | neweng, query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | On ubuntu:11111:
On ubuntu:22222:
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
If you run cloneCollection with copyindexes:false, the indexes are still copied. There is a message logged:
|
| Comments |
| Comment by Eric Milkie [ 05/Jul/19 ] |
|
cloneCollection is now deprecated as of 4.2 |
| Comment by David Storch [ 05/Jul/19 ] |
|
milkie, does the execution team own the cloneCollection command? (I don't think this ticket belongs on the query team backlog, but I'm not sure where it should go.) |
| Comment by auto [ 30/Oct/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 30/Oct/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |