[
https://issues.apache.org/jira/browse/DRILL-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979636#comment-14979636
]
Sudheesh Katkam commented on DRILL-3993:
----------------------------------------
[~julianhyde] I completely agree with you. I think my question could have been
phrased better. I wanted to know if there are any documented steps that we take
every time to catch up.
And thanks to the Calcite community for allowing Drillers to check for
regressions before a release; that's has been very helpful :)
> 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)
