-
Type:
Question
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:windows server 2012
It seems there is a issue in the latest mongo release 3.4.3. The code below was
working fine with Mongo version 3.2.9. But we run into the error with
3.4.3.
{aggregate([{ "$match" : {
"dtHeader.Equipment_ID" : NumberLong(7), "dtHeader.SnapshotType" : "Snapshot",
"dtHeader.RevolutionTimeStamp" : { "$gte" :
ISODate("2017-04-09T07:48:54.351Z"), "$lte" :
ISODate("2017-04-10T19:48:54.351Z") }, "dtHeader.RevolutionNumber" : {
"$gte" : 1, "$lte" : 1 } } }, { "$project" : { "RevolutionTimeStamp" :
"$dtHeader.RevolutionTimeStamp", "RevolutionNumber" :
"$dtHeader.RevolutionNumber", "Historians" : { },
"Statistics" : { "29_2" : "$dtStatistics.29.2" }, "ComputationEquipment" :
"$dtComputation_Equipment", "Annotations" : "$dtAnnotation", "ManualAnnotations"
: "$dtAnnotation_Manual" } }])}
Message = "Command aggregate failed: Invalid $project
specification: an empty object is not a valid value. Found empty object at path
Historians."