[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466542#comment-13466542
]
Namit Jain commented on HIVE-1977:
----------------------------------
It is making the code complicated.
Is the idea behind introducing a new conf. to handle the case if both
table.column and database.table are valid ?
Seems very unlikely, cant we create a hierarchy : database.table preceeds
table.column.
If the user really wants table.column in that case, they can always issue
database.table.column which does not have any ambiguities.
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
> --------------------------------------------------------------------------------
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
> Reporter: Carl Steinbach
> Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
