-
Type:
New Feature
-
Resolution: Duplicate
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Querying
-
None
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Hello,
Related page: https://docs.mongodb.org/manual/reference/operator/projection/positional/#array-field-limitation
Actually I can figure it out why this limitation is present. The issue might be regarding other operations. Especially `update`.
Is there any possibility of adding a new feature which providing usage of the second array field in the query document as a new feature in the feature?
(maybe by using sub-operator like `$arr1` and `$arr2`)
It seems as a private issue. However, cannot perform two-phase commits if an array value would be updated.
For instance;
var query = {
_id: t.customer_id,
invoices: { $elemMatch: { 'year': t.year, 'month': t.month } }
pendingTransactions: t._id
}
var update = {
'invoices.$.amount': 549,
$push: { pendingTransactions: t._id }
}
db.customers.update(query, update)
- duplicates
-
SERVER-18500 Resolve ambiguity of positional projections with multiple implicit array traversal predicates in certain cases
-
- Backlog
-
- related to
-
-
- Closed
-