[
https://issues.apache.org/jira/browse/DRILL-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329537#comment-16329537
]
ASF GitHub Bot commented on DRILL-3993:
---------------------------------------
Github user amansinha100 commented on the issue:
https://github.com/apache/drill/pull/1066
@vvysotskyi could you pls separate out the HashAggregate OOM related change
from this PR and file a separate JIRA for it since it is unrelated to the
calcite rebase per-se. Lumping them together causes confusion. Thanks.
> Rebase Drill on Calcite master branch
> -------------------------------------
>
> Key: DRILL-3993
> URL: https://issues.apache.org/jira/browse/DRILL-3993
> Project: Apache Drill
> Issue Type: Bug
> Components: Query Planning & Optimization
> Affects Versions: 1.2.0
> Reporter: Sudheesh Katkam
> Assignee: Roman Kulyk
> Priority: Major
>
> Calcite keeps moving, and now we need to catch up to Calcite 1.5, and ensure
> there are no regressions.
> Also, how do we resolve this 'catching up' issue in the long term?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
