[SERVER-6361] Disallow exclusion in $project for now Created: 09/Jul/12 Updated: 19/Mar/13 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: | Task | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
It isn't currently consistent with core query projections when using exclusions. This should be supported correctly for 2.3 |
| 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 |
| Comment by Mathias Stearn [ 16/Jul/12 ] |
|
There will be an exception to allow {_id:0, x:1} |