[
https://issues.apache.org/jira/browse/DRILL-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386021#comment-15386021
]
ASF GitHub Bot commented on DRILL-4682:
---------------------------------------
GitHub user vdiravka opened a pull request:
https://github.com/apache/drill/pull/549
DRILL-4682: Allow full schema identifier in SELECT clause
- changed SqlBracketlessSyntax logic in the DrillCompoundIdentifier;
- added checking of using full schema name in column names;
- added unit test testColumnNamesWithSchemaName;
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vdiravka/drill DRILL-4682
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/549.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #549
----
commit 0e5123c80e0b7d2dca36503dab3917bbae827702
Author: Vitalii Diravka <vitalii.dira...@gmail.com>
Date: 2016-06-13T11:44:33Z
DRILL-4682: Allow full schema identifier in SELECT clause
- changed SqlBracketlessSyntax logic in the DrillCompoundIdentifier;
- added checking of using full schema name in column names;
- added unit test testColumnNamesWithSchemaName;
----
> 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
>
> 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)
