You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Roman Kulyk (JIRA)" <ji...@apache.org> on 2017/11/22 11:49:00 UTC
[jira] [Comment Edited] (DRILL-3993) Rebase Drill on Calcite master
branch
[ https://issues.apache.org/jira/browse/DRILL-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262374#comment-16262374 ]
Roman Kulyk edited comment on DRILL-3993 at 11/22/17 11:48 AM:
---------------------------------------------------------------
Added link to local Drill branch which was rebased to Calcite 1.13:
https://github.com/KulykRoman/drill/tree/CalciteForkRebase_rc3
was (Author: romankulyk):
Added link to local Drill branch which was rebased to Calcite 1.13.
> Rebase Drill on Calcite master branch
> -------------------------------------
>
> 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
> Assignee: Roman Kulyk
>
> 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.4.14#64029)