[DRIVERS-167] Support $numberLong for extended JSON parsing and generation Created: 11/Jun/14  Updated: 27/May/22  Resolved: 08/Feb/16

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Barrie Segal
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-11867 In strict-json mode, represent Number... Closed
depends on CSHARP-995 Add support for reading new extended ... Closed
depends on PYTHON-708 Support new extended JSON types intro... Closed
depends on CDRIVER-375 Support $numberLong for extended JSON... Closed
depends on NODE-199 Support $numberLong for extended JSON... Closed
depends on RUBY-780 Support $numberLong for extended JSON... Closed
depends on JAVA-1272 Support reading MongoDB Extended JSON... Closed
Server Compat: 2.5
Driver Compliance:
Key Status/Resolution FixVersion
PYTHON-708 Done 2.8, 3.0
JAVA-1272 Done 2.12.3
CSHARP-995 Done 1.9.2
RUBY-780 Won't Fix 12_01_17
PERL-373 Done
PHP-1121 Done
CDRIVER-375 Done 0.96.4
NODE-199 Done

 Description   

This is related to SERVER-11867. Documentation is here:

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

Drivers that parse extended JSON should support $numberLong.



 Comments   
Comment by Jeffrey Yemin [ 20/Jun/14 ]

After going back and forth on this, I am now of the opinion that the least disruptive thing drivers can do (especially in a patch release) is to parse $numberLong, but not generate it. There is an open server ticket, SERVER-6812, which requests mongoexport flag(s) for controlling the output of BSON numeric types. We can wait for that ticket to be resolved, and take direction from it in terms of what flags our drivers should support for extended JSON export.

Apologies for any confusion.

Generated at Thu Feb 08 08:20:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.