-
Type:
Improvement
-
Resolution: Done
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Internal Code, Tools
-
None
It's not clear exactly what Extended JSON syntax is meant to be used for, but if anyone is trying to use it for backup or archiving purposes, they might reasonably care about preserving numeric type information (e.g., float/int32/int64 distinction), as well as any other BSON type we choose to introduce.
If we were to do this, I guess mongoexport should have a flag for whether to represent integers in JSON syntax (lossy, but backward compatible and better for interoperability with other JSON tools), or in Extended JSON syntax.
I suppose the same consideration would apply to the symbol type, though probably nobody uses that.
- depends on
-
SERVER-11867 In strict-json mode, represent NumberLongs with strings
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
SERVER-3483 $timestamp extended json format for dumping parts of the oplog
-
- Closed
-
-
-
- Implementing
-
-
-
- Closed
-
- related to
-
-
- Closed
-