[SERVER-8639] toJson produces incorrect shell TimeStamp constructor declaration Created: 20/Feb/13  Updated: 08/Mar/13  Resolved: 26/Feb/13

Status: Closed
Project: Core Server
Component/s: JavaScript, Tools
Affects Version/s: 2.4.0-rc0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Shaun Verch
Resolution: Incomplete Votes: 0
Labels: json, parser
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-7718 Timestamp constructor in shell should... Closed
is related to SERVER-7437 jsonString does not handle Timestamps... Closed
Operating System: ALL
Participants:

 Description   

$ ./bsondump dump/test/date.bson 
{ "_id" : Timestamp( 1361395091, 1 ) } // should be x1000 for millis constructor

See SERVER-7718 for background on this.

The current behavior will create incorrect TimeStamps in the shell.



 Comments   
Comment by Scott Hernandez (Inactive) [ 26/Feb/13 ]

yes, and we are fixing this in the js Timestamp constructor for RC2

Comment by Shaun Verch [ 26/Feb/13 ]

Timestamps before this version were handled as described in SERVER-7437. Given that the format of timestamps changed anyway, I don't think a user would be depending on this behavior.

Comment by Scott Hernandez (Inactive) [ 21/Feb/13 ]

This is a regression in behavior however I think it more correct and we should make it work by fixing the bug in the constructor (linked issue), not perpetuating the incorrect behavior/format.

Comment by Eliot Horowitz (Inactive) [ 21/Feb/13 ]

If this is a regression in 2.4, has to go in 2.4.
Otherwise 2.5.w

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