[ https://issues.apache.org/jira/browse/DRILL-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vitalii Diravka reassigned DRILL-4682: -------------------------------------- Assignee: Vitalii Diravka > 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)