[SERVER-12307] Provide a means in query framework to efficiently determine if a query is $isolated Created: 09/Jan/14 Updated: 16/Mar/16 Resolved: 11/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.3 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Benjamin Murphy |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Quint Iteration 7, Query 11 (03/14/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Right now, $isolated is handled as an expression tree node. When update wants to find out if the current op is $isolated, it needs to walk the children of the expression root. It would probably be better if something like CanonicalQuery obtained this information during the initial parse and cached it. The $isolated node probably doesn't need to stay in the tree. |
| Comments |
| Comment by Githook User [ 11/Mar/16 ] |
|
Author: {u'username': u'benjaminmurphy', u'name': u'Benjamin Murphy', u'email': u'benjamin_murphy@me.com'}Message: |
| Comment by Githook User [ 11/Mar/16 ] |
|
Author: {u'username': u'benjaminmurphy', u'name': u'Benjamin Murphy', u'email': u'benjamin_murphy@me.com'}Message: |
| Comment by J Rassi [ 01/Apr/15 ] |
|
The breakdown of work for this ticket is as follows:
As part of future work, we should make sure that non-update/non-delete user operations fail if a user attempts to use the $atmoic/$isolated operators as part of a query predicate. Filed |