bsondump currently produces invalid json for any
bson file that includes date objects. For example:
The Date ( ... ) bit will choke any validating JSON parser.
Additionally, by default the bsondump tool appends a line to the end
of the output that looks something like this:
Sun Aug 14 20:41:48 33 objects found
Again, this will choke any JSON parser that attempts to consume the
output. It would be better if this either wasn't included at all, was
sent to stderr or could be turned off with a --quiet command line
argument.
- duplicates
-
TOOLS-2257 Update bsondump to output canonical extended json
- Closed
- is duplicated by
-
TOOLS-138 bsondump does not produce valid json output
- Closed
- is related to
-
SERVER-9282 Audit tools for correct handling of log output
- Closed
- related to
-
SERVER-3112 mongo* tools logs should not log to stdout (broken w/--out -)
- Closed
-
TOOLS-138 bsondump does not produce valid json output
- Closed
-
SERVER-11813 In strict-json mode, represent dates with strings.
- Closed