[
https://issues.apache.org/jira/browse/DRILL-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014042#comment-14014042
]
Steven Phillips commented on DRILL-871:
---------------------------------------
Actually, I am saying, for Drill, it is not an error at all. It's not the query
you meant to run, but it is a perfectly valid query.
In postgres, tables have a well-defined schema, so it can give an error when
you select or join on a column that doesn't exist.
Drill tables do not have a well defined schema. So in this case, it is not
possible to say that the column "o.c_custkey" does not exist, because it might.
In other words, for a dynamic drill table, any column you request exists, and
in this case, every value is null.
> Drill fails to detect errors in queries
> ---------------------------------------
>
> Key: DRILL-871
> URL: https://issues.apache.org/jira/browse/DRILL-871
> Project: Apache Drill
> Issue Type: Bug
> Components: Functions - Hive
> Reporter: Zhiyong Liu
>
> Accidentally had a typo in a query, such as
> select o.O_TOTALPRICE, c.C_NAME
> from orders o, customer c
> where o.C_CUSTKEY = c.C_CUSTKEY and o.O_TOTALPRICE > 400000.00
> order by o.O_TOTALPRICE;
> The typo is o.C_CUSTKEY, which should be o.O_CUSTKEY. Drill executes the
> query with no error detected:
> 0: jdbc:drill:schema=dfs.TpcHMulti> select o.O_TOTALPRICE, c.C_NAME
> . . . . . . . . . . . . . . . . . > from orders o, customer c
> . . . . . . . . . . . . . . . . . > where o.C_CUSTKEY = c.C_CUSTKEY and
> o.O_TOTALPRICE > 400000.00
> . . . . . . . . . . . . . . . . . > order by o.O_TOTALPRICE;
> +--+
> | |
> +--+
> +--+
> No rows selected (1.161 seconds)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
