[SERVER-17312] Collmod must persist all supported options, regardless of current storage engine Created: 17/Feb/15 Updated: 18/Sep/15 Resolved: 20/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0-rc9, 3.1.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Minor Change | ||||||||
| Backport Completed: | |||||||||
| Participants: | |||||||||
| Description |
|
Currently, there are only two supported storage engine specific options: usePowerOf2Sizes and noPadding. These should both effect the options.flags field of the collection as seen by the listCollections command. For now all other options will be rejected. A general solution to allow arbitrary engine-specific options (similar to createCollection) will be designed for 3.2. |
| Comments |
| Comment by Githook User [ 20/Feb/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: For the two currently supported engine-specific options, the collmod command This removes the ability of storage engines to have custom options that can (cherry picked from commit ae18bbec33db1c4bf57d328505474eb7bba517df) Conflicts: |
| Comment by Githook User [ 20/Feb/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: For the two currently supported engine-specific options, the collmod command This removes the ability of storage engines to have custom options that can |