Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 15 Sep 2015 19:22:46 +0000 (UTC)
From: "Khurram Faraaz (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12848382.1437599493000.345294.1442344966195@Atlassian.JIRA>
In-Reply-To: <JIRA.12848382.1437599493000@Atlassian.JIRA>
References: <JIRA.12848382.1437599493000@Atlassian.JIRA>
 <JIRA.12848382.1437599493318@arcas>
Subject: [jira] [Closed] (DRILL-3542) Rebase Drill on Calcite 1.4.0 release
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DRILL-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Khurram Faraaz closed DRILL-3542.
---------------------------------

> Rebase Drill on Calcite 1.4.0 release
> -------------------------------------
>
>                 Key: DRILL-3542
>                 URL: https://issues.apache.org/jira/browse/DRILL-3542
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Query Planning & Optimization
>            Reporter: Jinfeng Ni
>            Assignee: Aman Sinha
>             Fix For: 1.2.0
>
>
> DRILL-1384 rebase Drill on Calcite from 0.9 to 1.1. However, since the most recent of Calcite is 1.4.0-SNAPSHOT,  Drill has to move forward with the Calcite library again.
> Once we finish the rebasing, if there are regressions on Drill side, this JIRA will  be used as umbrella JIRA and we will create each individual JIRA for one category of regression, and link those JIRA(s) here.  This is different from the way DRILL-1384 worked, where we mixed the fix together, making it hard to understand the reason of each code change during the rebasing effort.  


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)