Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 17 Mar 2015 00:00:48 +0000 (UTC)
From: "Aman Sinha (JIRA)" <jira@apache.org>
To: dev@drill.apache.org
Message-ID: <JIRA.12782420.1426550424000.111287.1426550448943@Atlassian.JIRA>
In-Reply-To: <JIRA.12782420.1426550424000@Atlassian.JIRA>
References: <JIRA.12782420.1426550424000@Atlassian.JIRA>
 <JIRA.12782420.1426550424562@arcas>
Subject: [jira] [Created] (DRILL-2479) Correlated EXISTS containing an IN
 subquery fails to plan
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aman Sinha created DRILL-2479:
---------------------------------

             Summary: Correlated EXISTS containing an IN subquery fails to plan
                 Key: DRILL-2479
                 URL: https://issues.apache.org/jira/browse/DRILL-2479
             Project: Apache Drill
          Issue Type: Bug
    Affects Versions: 0.8.0
            Reporter: Aman Sinha
            Assignee: Aman Sinha
             Fix For: 0.9.0


The following correlated EXISTS query gives a CannotPlanException : 
{code}
 select count(*) from lineitem l where exists (select ps.ps_suppkey from partsupp ps where ps.ps_suppkey = l.l_suppkey and ps.ps_partkey in (select p.p_partkey from part p));
{code}
The query succeeds if the IN clause in the EXISTS subquery is removed or replaced with an IN list of constants.  It also succeeds on the latest version of Calcite.  Drill is quite out of date with Calcite and there were decorrelation related changes in Calcite sometime mid to late 2014.  This issue should get resolved once Drill is rebased on recent Calcite. 


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