[SERVER-19015] Dissallow convertToCapped on capped collections Created: 17/Jun/15 Updated: 14/Mar/17 Resolved: 19/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Adam Midvidy |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | fuzzer-blacklist, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||
| Sprint: | Integration F (02/01/16) | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
This causes potential problems since:
So instead we should return an error that the collection is already capped and the operation did not complete. |
| Comments |
| Comment by Adam Midvidy [ 19/Jan/16 ] |
|
Closing as WONTFIX due to 2 issues: (1): it will lead to a crash during upgrade if a convertToCapped command is |