[SERVER-16819] JSON configuration file Created: 13/Jan/15 Updated: 14/Jan/15 Resolved: 14/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Andrew Ryder (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Request to support JSON as the format for MongoD and MongoS configuration files. This is a natural choice for the configuration file of a server product that uses JSON extensively. It can use the existing schema directly but in JSON syntax - the conversion is direct, one-to-one. |
| Comments |
| Comment by Andrew Ryder (Inactive) [ 14/Jan/15 ] |
|
Brilliant. That makes perfect sense. |
| Comment by Eric Milkie [ 13/Jan/15 ] |
|
YAML subsumes JSON: http://en.wikipedia.org/wiki/YAML#JSON |