Github user rchallapalli commented on the issue:
https://github.com/apache/drill/pull/822
Based on the current design, if the code senses that there is not
sufficient memory then it goes back to the old code. Now I have encountered a
case where this happened and the old agg did not respect the memory constraints
imposed by me. I gave 116MB memory and the old hash agg code consumed ~130MB
and completed the query. This doesn't play well with the overall resource
management plan
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
