[
https://issues.apache.org/jira/browse/DRILL-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025568#comment-16025568
]
ASF GitHub Bot commented on DRILL-5457:
---------------------------------------
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
> Support Spill to Disk for the Hash Aggregate Operator
> -----------------------------------------------------
>
> Key: DRILL-5457
> URL: https://issues.apache.org/jira/browse/DRILL-5457
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Relational Operators
> Affects Versions: 1.10.0
> Reporter: Boaz Ben-Zvi
> Assignee: Boaz Ben-Zvi
> Fix For: 1.11.0
>
>
> Support gradual spilling memory to disk as the available memory gets too
> small to allow in memory work for the Hash Aggregate Operator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
