-
Type:
Improvement
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Querying
-
Labels:None
-
Query 10 (02/22/16)
-
(copied to CRM)
Running the following commands on 2.6 and 2.4 gives different output when running following commands:
db.createCollection("PositionalOperatorRepro") db.PositionalOperatorRepro.insert({"_id": "test1", "Items": [ { "Id": 1 }, { "Id": 2 } ] }) db.PositionalOperatorRepro.find({ "_id" : "test1", "Items" : { "$exists" : true, "$elemMatch" : { "Id" : 2 } } } , { "Items.$" : 1 })
// 2.4 returns
{.. Items: [{Id:2}]}
// 2.6 returns
{.. Items: [{Id:1}]}
// 2.6 without $exists
{.. Items: [{Id:2}]}
If we remove the "$exists" : true criteria the output will be the same.
Is this change documented anywhere? There could be compatibility issues when upgrading.
I'm attaching a screen shot where I reproduced this behavior.
- is duplicated by
-
SERVER-17159 $ Positional Operator Only Updating First Sub-Document
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-21794 Array field limitation in query document [Only one array field may appear in the query document.]
-
- Closed
-
-
-
- Backlog
-
- related to
-
DOCS-12773 Explicitly refer to "Single Field Matches" for positional "$ (update)" operator
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-