[
https://issues.apache.org/jira/browse/DRILL-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979492#comment-14979492
]
Jinfeng Ni commented on DRILL-3993:
-----------------------------------
[~jnadeau], that's the three major things between Drill's forked Calcite and
Calcite master. I'm working on the fist one.
The third one, AbstractConverter, is also one of the reason for Drill's long
physical planning time in some cases. If we remove AbstractConverter and find
way for trait pull-up, I believe we could see planning time would be reduced
significantly.
> 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)
