You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Jacques Nadeau (JIRA)" <ji...@apache.org> on 2015/03/20 21:48:38 UTC

[jira] [Updated] (DRILL-2258) IN operator on top of data with schema changes results in "Hash Join does not support schema changes"

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

Jacques Nadeau updated DRILL-2258:
----------------------------------
    Fix Version/s: Future

> 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: Improvement
>          Components: Execution - Relational Operators
>            Reporter: Rahul Challapalli
>            Assignee: Chris Westin
>             Fix For: Future
>
>         Attachments: error.log, file1.json, file2.json, file3.json
>
>
> 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)