[SERVER-13209] Ensure extended shell JSON ouput format round trips through the shell Created: 14/Mar/14  Updated: 26/Oct/21  Resolved: 26/Oct/21

Status: Closed
Project: Core Server
Component/s: JavaScript, Shell
Affects Version/s: 2.5.5
Fix Version/s: None

Type: Improvement Priority: Trivial - P5
Reporter: Shaun Verch Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-19171 Shell does not always use extended JS... Closed
related to SERVER-16618 Log file should print extended json c... Backlog
related to SERVER-6813 Shell support for Extended JSON Closed
is related to SERVER-19747 MinKey/MaxKey not printing as JSON in... Closed
is related to SERVER-24562 Enhance shell to output strict json Closed
Participants:

 Description   

Not all BSON types are representable in unmodified JSON, which is why we have:

http://docs.mongodb.org/manual/reference/mongodb-extended-json/

Note the two types, "strict", which is RFC compliant JSON, and "shell", which in theory is parseable by the shell. "strict" is output almost everywhere, except for "bsondump", which outputs "shell" mode BSON.

The "shell" mode seems to be parseable by the shell, but at least one BSON type, "date", gets output as "Date", when "ISODate" or "new Date" is how the shell represents the actual BSON date type. This is an example of one place where the types do not correctly round trip, but there may be more.


Generated at Thu Feb 08 03:30:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.