You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/04/04 14:13:00 UTC

[jira] [Commented] (DRILL-8412) Upgrade to Calcite 1.35-SNAPSHOT

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

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

jnturton commented on PR #2776:
URL: https://github.com/apache/drill/pull/2776#issuecomment-1496047719

   Can someone do the formailty of approving so that we can give this a try?




> Upgrade to Calcite 1.35-SNAPSHOT
> --------------------------------
>
>                 Key: DRILL-8412
>                 URL: https://issues.apache.org/jira/browse/DRILL-8412
>             Project: Apache Drill
>          Issue Type: Task
>          Components: SQL Parser
>            Reporter: James Turton
>            Assignee: James Turton
>            Priority: Major
>
> This issue proposes that we try basing Drill master on snapshot builds of the upcoming version of Calcite so that the CI tests that run automatically upon commits to master will exercise Drill with present day Calcite.
> 1. The CI tests that run automatically upon commits to Drill master will exercise Drill with present day Calcite.
> 2. Breaking changes in Calcite would (mostly) break the Drill CI and force us to deal with them in order to proceed.
> 3. Regressions in Calcite would (mostly) break the Drill CI and force to report them in order to proceed.
> 4. If Drill master becomes too unstable when it is based on Calcite snapshots then this change is trivially undoable.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)