[
https://issues.apache.org/jira/browse/DRILL-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282190#comment-14282190
]
Jinfeng Ni commented on DRILL-2030:
-----------------------------------
Thanks for finding this problem. Yes, you are right. The top level project
should be below Writer. Originally, I thought both Screen and Writer could be
root operator; Screen is the root operator for query, while Writer is is the
root for CTAS. Apparently, later on we decided to put Writer under Screen, so
that Screen could report back the result of CTAS, which broke the logic of star
column handling.
I'll submit a patch to fix this issue.
> CTAS with SELECT * and expression creates column names with prefix
> ------------------------------------------------------------------
>
> Key: DRILL-2030
> URL: https://issues.apache.org/jira/browse/DRILL-2030
> Project: Apache Drill
> Issue Type: Bug
> Components: Query Planning & Optimization
> Affects Versions: 0.7.0
> Reporter: Aman Sinha
> Assignee: Jinfeng Ni
>
> Doing a CTAS with the star column and an expression creates columns that
> contain the table prefix 'T||' . Looks like the top project did not strip
> out the prefix.
> {code}
> 0: jdbc:drill:zk=local> create table region4 as select *, r_regionkey + 1
> from cp.`tpch/region.parquet`;
> +------------+---------------------------+
> | Fragment | Number of records written |
> +------------+---------------------------+
> | 0_0 | 5 |
> +------------+---------------------------+
> 0: jdbc:drill:zk=local> select * from region4;
> +-----------------+------------+---------------+------------+
> | T2¦¦r_regionkey | T2¦¦r_name | T2¦¦r_comment | EXPR$1 |
> +-----------------+------------+---------------+------------+
> {code}
> The column names are correct if there is a regular column with the star
> column.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
