[
https://issues.apache.org/jira/browse/DRILL-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214238#comment-14214238
]
Jacques Nadeau commented on DRILL-1726:
---------------------------------------
I would like to do that. The resolution happens in the Calcite (Optiq) code
and there are lots of layers in between so I think it is no trivial to address.
[~julianhyde], what do you think? We generate a new Identifier type and then
currently forcefully convert that to a collection of Item operators based on
the pattern. It seems like we'd need to rethink the approach to be able to
handle this ambiguity.
> Query fails when table is not named
> -----------------------------------
>
> Key: DRILL-1726
> URL: https://issues.apache.org/jira/browse/DRILL-1726
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Tomer Shiran
>
> The first query failed, and the second succeeded. The only difference was
> that the field was referred to with the table name b (ie, b.hours.Friday vs.
> hours.Friday). Both should work.
> {code}
> 0: jdbc:drill:zk=localhost:2181> SELECT name, hours.Friday FROM
> dfs.root.`Users/tshiran/Development/demo/data/yelp/business.json` b LIMIT 1;
> Query failed: Failure while running sql.
> Error: exception while executing query: Failure while executing query.
> (state=,code=0)
> 0: jdbc:drill:zk=localhost:2181> SELECT name, b.hours.Friday FROM
> dfs.root.`Users/tshiran/Development/demo/data/yelp/business.json` b LIMIT 1;
> +------------+------------+
> | name | EXPR$1 |
> +------------+------------+
> | Eric Goldberg, MD | {"close":"17:00","open":"08:00"} |
> +------------+------------+
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
