[SERVER-6177] verify assertion when parent of an inclusion field is an operator expression Created: 22/Jun/12 Updated: 11/Jul/16 Resolved: 20/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
ExpressionObject::includePath expects that an existing expression encountered while traversing the supplied field path is an ExpressionObject. But this will not be the case if an earlier expression on the field was a non object expression (it could be an operator expression). Current behavior: verify assertion in the case described above, and in the test
|
| Comments |
| Comment by auto [ 20/Jul/12 ] |
|
Author: {u'date': u'2012-07-14T12:04:12-07:00', u'email': u'mathias@10gen.com', u'name': u'Mathias Stearn'}Message: Rewrite ExpressionObject The main difference between this version and the old is that the following // classic inclusion // nested inclusion {'a.b': '$a.b'} // dotted FieldPathExpression // nested FieldPathExpression Additionally support for exclusion of fields other than _id has been Other related bugs:
Remaining TODOs: Disabled test for |