[DOCS-3879] Change in mongoexport output format for dates Created: 07/Aug/14 Updated: 30/Apr/15 Resolved: 12/Sep/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-2.6 |
| Fix Version/s: | v1.3.11, mongodb-2.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Kangas | Assignee: | Andrew Aldridge |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 8 years, 41 weeks, 6 days ago | ||||||||||||||||
| Description |
|
This means that mongoexport in 2.6 now produces different output for date values.
The value is ISO-8601 format using the local timezone of the system mongoexport is running on. We failed to document this change for the 2.6 release. This is a breaking change to any programs that were consuming the output of mongoexport. Related parsing changes: |
| Comments |
| Comment by Ethan Lacey [ 30/Apr/15 ] | ||||||||
|
It's a fair question, does 2.6 or 3.0 offer the ability to retain backwards compatibility with 2.4 date formats? As you would guess, any large scale data integration is driven by a dump, not API, which this breaks. | ||||||||
| Comment by Michael Paik [ 30/Mar/15 ] | ||||||||
|
cgopalan@sailthru.com, to make that feature request you'll need to open a server tools ticket under the TOOLS project. | ||||||||
| Comment by Chandrakant Gopalan [ 26/Mar/15 ] | ||||||||
|
Hello, Thanks | ||||||||
| Comment by Githook User [ 12/Sep/14 ] | ||||||||
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: | ||||||||
| Comment by Githook User [ 12/Sep/14 ] | ||||||||
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> | ||||||||
| Comment by Frej Bjon [ 08/Aug/14 ] | ||||||||
|
To point out a related effect, the behaviour is different for pre-1970 dates:
| ||||||||
| Comment by Jeffrey Yemin [ 07/Aug/14 ] | ||||||||
|
Also note that this change effectively alters the specification for MongoDB Extended JSON Format, which states that the value of $date is an Int64: http://docs.mongodb.org/manual/reference/mongodb-extended-json/#date |