[SERVER-6650] should matcher prevent use of $ prefixed field names? Created: 30/Jul/12 Updated: 11/Jul/16 Resolved: 16/Jun/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Right now if someone attempts to use an aggregation expression inside a query or inside a $match, they will see results different from what they expect (and no error):
In both cases { $add:[ 1, 1 ] }is treated as a document to compare against, not an expression to be evaluated. |
| Comments |
| Comment by Mathias Stearn [ 27/Aug/12 ] |
|
Moving from Agg framework to Querying because this deals with the general Matcher class, not an agg specific version. |
| Comment by auto [ 24/Aug/12 ] |
|
Author: {u'date': u'2012-08-02T13:35:55-07:00', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |
| Comment by Aaron Staple [ 30/Jul/12 ] |
|
Scheduled in rc1 for triage. |