Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Wed, 18 Feb 2015 00:05:13 +0000 (UTC)
From: "Rahul Challapalli (JIRA)" <jira@apache.org>
To: dev@drill.apache.org
Message-ID: <JIRA.12775777.1424217901000.70127.1424217913401@Atlassian.JIRA>
In-Reply-To: <JIRA.12775777.1424217901000@Atlassian.JIRA>
References: <JIRA.12775777.1424217901000@Atlassian.JIRA>
 <JIRA.12775777.1424217901857@arcas>
Subject: [jira] [Created] (DRILL-2258) IN operator on top of data with
 schema changes results in "Hash Join does not support schema changes"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Rahul Challapalli created DRILL-2258:
----------------------------------------

             Summary: IN operator on top of data with schema changes results in "Hash Join does not support schema changes"
                 Key: DRILL-2258
                 URL: https://issues.apache.org/jira/browse/DRILL-2258
             Project: Apache Drill
          Issue Type: Bug
          Components: Query Planning & Optimization
            Reporter: Rahul Challapalli
            Assignee: Jinfeng Ni


git.commit.id.abbrev=6676f2d

The data set contains multiple files with schema changes among them. By schema changes I refer to adding/removing fields

The below query fails :
{code}
select * from `schema_changes` where 2 in (select flatten(lst_lst[0]) from `schema_changes`);
Query failed: Query stopped., Hash join does not support schema changes [ 4859e87a-74a6-49a0-aa62-1f0d2033b038 on qa-node190.qa.lab:31010 ]
{code}

However when I select explicit fields from the same data set there seems to be no issues.


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