[jira] [Commented] (DRILL-4682) Allow full schema identifier in SELECT clause

["Volodymyr Vysotskyi (JIRA)" <ji...@apache.org>]

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

Volodymyr Vysotskyi commented on DRILL-4682:
--------------------------------------------

Another case which should be considered is when we have a table {{t1}} in {{dfs}} plugin and this table contains field {{a}} and map {{t1}} which contains child {{a}}, so currently query
{code:sql}
select dfs.t1.a from dfs.t1 as dfs
{code}
is unambiguous and will return the value of the nested field {{t1.a}}, but with this change, it may be either root field {{a}} or nested in {{t1}} field {{a}}.

So if we will allow such syntax, we should determine the rules to handle such cases.

> Allow full schema identifier in SELECT clause
> ---------------------------------------------
>
>                 Key: DRILL-4682
>                 URL: https://issues.apache.org/jira/browse/DRILL-4682
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: SQL Parser
>            Reporter: Andries Engelbrecht
>            Assignee: Vitalii Diravka
>            Priority: Major
>
> Currently Drill requires aliases to identify columns in the SELECT clause when working with multiple tables/workspaces.
> Many BI/Analytical and other tools by default will use the full schema identifier in the select clause when generating SQL statements for execution for generic JDBC or ODBC sources. Not supporting this feature causes issues and a slower adoption of utilizing Drill as an execution engine within the larger Analytical SQL community.
> Propose to support 
> SELECT <storage_plugin>.<workspace>.<table>.<column> FROM <storage_plugin>.<workspace>.<table>
> Also see DRILL-3510 for double quote support as per ANSI_QUOTES
> SELECT "<storage_plugin>"."<workspace>"."<table>"."<column>" FROM "<storage_plugin>"."<workspace>"."<table>"
> Which is very common generic SQL being generated by most tools when dealing with a generic SQL data source.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)