[SERVER-4968] Aggregation fails with ambiguous assertion when applied to a collection with forbidden BSON types Created: 14/Feb/12 Updated: 15/Aug/12 Resolved: 01/Mar/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | 2.1.0 |
| Fix Version/s: | 2.1.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Chris Westin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
If you run aggregate on a collection containing one of the following fields
Example:
Server output:
This error will happen if an illegal type is in any of the documents passed into aggregation. Should be documented and improve the error message. |
| Comments |
| Comment by auto [ 12/Jul/12 ] |
|
Author: {u'date': u'2012-06-29T16:49:56-07:00', u'email': u'mathias@10gen.com', u'name': u'Mathias Stearn'}Message: If there is an early simple $project, apply it before converting to Documents This is a partial fix for This also provides a workaround for objects with types that aren't This commit will need some doc updates, in particular in the "Optimizing |
| Comment by auto [ 01/Mar/12 ] |
|
Author: {u'login': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 01/Mar/12 ] |
|
Author: {u'login': u'cwestin', u'name': u'U-tellus\\cwestin', u'email': u'cwestin@10gen.com'}Message: |
| Comment by Chris Westin [ 25/Feb/12 ] |
|
Ideally, we wouldn't bring these values into the pipeline at all if they aren't referenced, per |