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, 21 Dec 2017 13:38:01 GMT

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

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

Github user vvysotskyi commented on a diff in the pull request:

    https://github.com/apache/drill/pull/1066#discussion_r158263816
  
    --- Diff: exec/jdbc-all/pom.xml ---
    @@ -572,7 +572,7 @@
                               This is likely due to you adding new dependencies to a java-exec
and not updating the excludes in this module. This is important as it minimizes the size of
the dependency of Drill application users.
     
                             </message>
    -                        <maxsize>29000000</maxsize>
    +                        <maxsize>31000000</maxsize>
    --- End diff --
    
    We didn't have problems on our local machines or test cluster connected with `maxsize`
after changing it to 31000000. Which version of Maven did you use? 
    Anyway, I have increased it to 32000000.


> 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
>
> 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
(v6.4.14#64029)

Mime
View raw message