[DOCS-3525] Bad Logic in Hierarchical aggregation use-case example Created: 02/Jun/14 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Jones | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | aggregation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Description |
|
Have tried to implement a hierarchical aggregation system as described at http://docs.mongodb.org/ecosystem/use-cases/hierarchical-aggregation/ but have discovered that the logic doesn't seem to be correct. Have attached a text file with an example of the process failing. It seems that it may function correctly only if the aggregations are very carefully scheduled, rather than being an incremental process that can be run as often as necessary as implied. |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |