[SERVER-6269] DocumentSourceUnwind does not implement the DocumentSource iterator interface correctly Created: 01/Jul/12 Updated: 11/Jul/16 Resolved: 13/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
DocumentSourceUnwind does not advance properly if getCurrent() is not called before advance(). And there may be a problem with eof() if pUnwindValue is set but pUnwinder is exhausted. Observed behavior: An incorrect result set may be generated for pipelines involving $unwind, particularly if used in conjunction with $skip. Test:
|
| Comments |
| Comment by auto [ 22/Jul/13 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: DocumentSourceCursor should be limit-aware Follow-up to |
| Comment by auto [ 13/Jul/12 ] |
|
Author: {u'date': u'2012-07-13T14:57:59-07:00', u'email': u'aaron@10gen.com', u'name': u'Aaron'}Message: |