[
https://issues.apache.org/jira/browse/DRILL-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701147#comment-17701147
]
ASF GitHub Bot commented on DRILL-8412:
---------------------------------------
jnturton opened a new pull request, #2776:
URL: https://github.com/apache/drill/pull/2776
# [DRILL-8412](https://issues.apache.org/jira/browse/DRILL-8412): Upgrade to
Calcite 1.35-SNAPSHOT
## Description
If we're willing to try basing Drill master on snapshot builds of the
upcoming version of Calcite for a while then here's a PR to do that. Please see
the related discussion in Drill and Calcite mailing lists this week for more
information.
Important notes.
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 PR is trivially undoable.
## Documentation
N/A
## Testing
Existing unit test suite.
> 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.
> Breaking changes in Calcite would (mostly) break the Drill CI and force us to
> deal with them in order to proceed.
> Regressions in Calcite would (mostly) break the Drill CI and force to report
> them in order to proceed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
