drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-3993) Rebase Drill on Calcite master branch
Date Thu, 18 Jan 2018 10:56:03 GMT

    [ https://issues.apache.org/jira/browse/DRILL-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330379#comment-16330379
] 

ASF GitHub Bot commented on DRILL-3993:
---------------------------------------

Github user vvysotskyi commented on the issue:

    https://github.com/apache/drill/pull/1066
  
    @amansinha100, regarding HashAggregate OOM related change, it was done in the scope of
this pull request since with new Calcite a physical plan for the query was changed to the
correct one but it caused an infinite loop in HashAgg operator. Therefore I made these changes
in order to prevent this infinite loop for the queries that previously worked. 
    I still think that it is better to keep this change in this PR.


> 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 &amp; 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)

Mime
View raw message