[
https://issues.apache.org/jira/browse/DRILL-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636036#comment-14636036
]
Sean Hsuan-Yi Chu commented on DRILL-3509:
------------------------------------------
I have difficulty reproducing your observation. Can you give me more detailed
information?
1. Do you have * in your select list?
2. Is the left side a directory also?
3. Do both sides point to json?
4. Is your query a simple union all like the below:
{code}
select a from dfs.`/root/left` union all select a from dfs.`/root/right`;
{code}
Or Union-All is a subquery below a main query such as:
{code}
selec a from
(
select a from dfs.`/root/left` union all select a from dfs.`/root/right`;
)
{code}
> Empty JSON files trigger exception when used in a union
> -------------------------------------------------------
>
> Key: DRILL-3509
> URL: https://issues.apache.org/jira/browse/DRILL-3509
> Project: Apache Drill
> Issue Type: Bug
> Components: Query Planning & Optimization
> Affects Versions: 1.1.0
> Reporter: Stefán Baxter
> Assignee: Sean Hsuan-Yi Chu
> Fix For: 1.2.0
>
>
> When the right hand side of a union is a directory search that involving an
> empty json file (or a empty log file waiting for first log lines) causes this
> exception:
> {
> "errorMessage" : "PARSE ERROR: From line 1, column 564 to line 1, column
> 574: Column 'occurred_at' not found in any table\n\n\n[Error Id:
> bef7370a-3c4e-4c35-8126-33c391ecb8ce on localhost:31010]"
> }
> where 'occurred_at' is the first column used/requested.
> This works fine if no union is involved but it happens regardless of the
> left/right position of the directory search if union is being called.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
