-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: JavaScript
-
None
-
Fully Compatible
-
ALL
-
Platform 7 08/10/15
Against master:
> MinKey [object MinKey] > MaxKey [object MaxKey] > tojson(MinKey) [object MinKey] > tojson(MaxKey) [object MaxKey]
The corresponding historical output (eg. in 3.1.6) is:
> MinKey { "$minKey" : 1 } > MaxKey { "$maxKey" : 1 } > tojson(MinKey) { "$minKey" : 1 } > tojson(MaxKey) { "$maxKey" : 1 }
Among other things, leads to strangeness in the output of sh.status():
... { "_id" : "test", "primary" : "shard0000", "partitioned" : true } test.test1 shard key: { "_id" : 1 } chunks: shard0000 1 >>>>>>>>>> { "_id" : [object MinKey] } -->> { "_id" : [object MaxKey] } on : shard0000 Timestamp(1, 0) ...
Whereas this used to be:
... { "_id" : "test", "primary" : "shard0000", "partitioned" : true } test.test1 shard key: { "_id" : 1 } chunks: shard0000 1 >>>>>>>>>> { "_id" : { "$minKey" : 1 } } -->> { "_id" : { "$maxKey" : 1 } } on : shard0000 Timestamp(1, 0) ...
- related to
-
SERVER-19171 Shell does not always use extended JSON Shell Syntax
- Closed
-
SERVER-13209 Ensure extended shell JSON ouput format round trips through the shell
- Closed