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

ASF GitHub Bot commented on DRILL-4682:
---------------------------------------

vdiravka commented on issue #549: DRILL-4682: Allow full schema identifier in 
SELECT clause
URL: https://github.com/apache/drill/pull/549#issuecomment-396147217
 
 
   @ilooner Yes, I am. It is in my backlog. The last status for it in my recent 
[comment](https://issues.apache.org/jira/browse/DRILL-4682?focusedCommentId=16483749&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16483749)
 for DRILL-4682.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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)

Reply via email to