[
https://issues.apache.org/jira/browse/DRILL-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731677#comment-14731677
]
Victoria Markman commented on DRILL-1395:
-----------------------------------------
Verified fixed in 1.2.0
#Fri Sep 04 00:17:59 UTC 2015
git.commit.id.abbrev=9baec8a
Test added in: Functional/Passing/union_all/negative
> 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
> Assignee: Sean Hsuan-Yi Chu
> Priority: Minor
> Fix For: 1.2.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)
