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/01/04 22:28:50 UTC
[jira] [Updated] (DRILL-1395) UNION ALL query fails "while setting
up Foreman"
[ https://issues.apache.org/jira/browse/DRILL-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Nadeau updated DRILL-1395:
----------------------------------
Fix Version/s: 1.0.0
Priority: Minor (was: Major)
> UNION ALL query fails "while setting up Foreman"
> ------------------------------------------------
>
> Key: DRILL-1395
> URL: https://issues.apache.org/jira/browse/DRILL-1395
> Project: Apache Drill
> Issue Type: Bug
> Components: Query Planning & Optimization
> Affects Versions: 0.5.0
> Reporter: Bob Rumsby
> Priority: Minor
> Fix For: 1.0.0
>
>
> The two sides of the UNION are not equivalent because one of the files has an additional column, but Aman tells me that this should work in a schema-less environment anyway. (I was expecting it to fail but with a more meaningful error because I am used to relational database UNION queries where a corresponding number of columns is expected on either side of the UNION operator.)
> The query fails whether or not the LIMIT is applied. EXPLAIN for this query also fails.
> 0: jdbc:drill:> select * from `clicks/clicks.campaign.json` union all select * from `clicks/clicks.json` limit 5;
> Query failed: Failure while setting up Foreman. DrillUnionRel#23471 [159a4852-e190-4edf-b11e-2d62db8efbd7]
> Error: exception while executing query: Failure while trying to get next result batch. (state=,code=0)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)