[SERVER-17320] Need a way for collmod to support arbitrary storageEngine-specific options Created: 18/Feb/15 Updated: 06/Dec/22 Resolved: 15/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
This needs to handle validation in a similar way to options specified at collection creation time. All new engine-specific options must be namespaced. |
| 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 |
| Comment by Mathias Stearn [ 18/Feb/15 ] |
|
|