drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Hsuan-Yi Chu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-3019) Extra column in Schema of Recordbatch from scanning Values
Date Fri, 22 May 2015 16:09:17 GMT

    [ https://issues.apache.org/jira/browse/DRILL-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556371#comment-14556371
] 

Sean Hsuan-Yi Chu commented on DRILL-3019:
------------------------------------------

To clarify, the degradation is a separate issue. Please refer to DRILL-3117.

This issue is meant to eliminate the extra column.

> Extra column in Schema of Recordbatch from scanning Values 
> -----------------------------------------------------------
>
>                 Key: DRILL-3019
>                 URL: https://issues.apache.org/jira/browse/DRILL-3019
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - Other
>            Reporter: Sean Hsuan-Yi Chu
>            Assignee: Sean Hsuan-Yi Chu
>         Attachments: DRILL-3019.1.patch
>
>
> A query which has a pattern:
> column IN (1, 1 + 1, 1 + 2)
> For the tuple, Calcite makes a plan like
> {code}
> UnionAll(all=[true])
>   UnionAll(all=[true])
>     Project(EXPR$0=[+(1, 1)])
>       Values
>     Project(EXPR$0=[+(1, 2)])
>       Values
>   Values
> {code}
> At execution, the schema of the recordbatch from scanning Values is [`ZERO`(BIGINT: OPTIONAL),
 `*`(BIGINT: OPTIONAL)].
> The second column (i.e., `*`) is not supposed to be there.



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

Mime
View raw message