drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-4682) Allow full schema identifier in SELECT clause
Date Tue, 02 Aug 2016 22:14:20 GMT

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

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

Github user jinfengni commented on the issue:

    https://github.com/apache/drill/pull/549
  
    I feel it might be better to work on this issue after Drill rebases Calcite. I debugged
a bit in SqlValidator, and seem that the code in Drill's forked Calcite is different from
what Calcite master has. It's possible that some of patches (star column) in Drill's forked
Calcite changes the behavior, and hence run into problem with the subquery cases.  Since star
column logic has been merged to Calcite master, it's better to try with this patch after rebasing
on top of Calcite master, in stead of coming up with a temporary solution with restrictions.

       



> 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
>
> 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
(v6.3.4#6332)

Mime
View raw message