[
https://issues.apache.org/jira/browse/DRILL-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979538#comment-14979538
]
Julian Hyde commented on DRILL-3993:
------------------------------------
[~sudheeshkatkam], "Catching up" is always necessary when you separate two
components into modules and version them separately. Changes in module A don't
break module B's nightly builds, but B needs to periodically sync up, at a time
of its choosing.
I think that we put a lot of valuable features into Calcite that benefit Drill
(some of them contributed by people who are also Drill committers), and I think
we do a pretty good job at controlling change, so that things that do not
directly benefit Drill at least do not break it. For example, we follow
semantic versioning and do not remove APIs except in a major release.
We have discovered with other projects that asking the downstream projects to
kick the tires of a Calcite release in the run-up to a release is an effective
way to find problems, and efficient in terms of time and effort for both
projects.
If there is anything else we can do in Calcite do make the process more
efficient for Drill, let me know.
> Rebase Drill on Calcite 1.5.0 release
> -------------------------------------
>
> 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
>
> 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.3.4#6332)
