[
https://issues.apache.org/jira/browse/SPARK-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037809#comment-14037809
]
Yin Huai commented on SPARK-2177:
---------------------------------
Generally Hive generates results of DDL statements as plain text (unless we use
"set hive.ddl.output.format=json"). It is not quite easy to parse those plain
strings and I think it is not a good idea to understand how Hive works for
every describe commands and write our code to generate the exactly same output.
With changes made in this PR, Spark SQL can support a subset of describe
commands which are commonly used. This subset is defined by
{code}
DESCRIBE [EXTENDED] [db_name.]table_name
{code}
All other cases are still treated as native commands.
> describe table result contains only one column
> ----------------------------------------------
>
> Key: SPARK-2177
> URL: https://issues.apache.org/jira/browse/SPARK-2177
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Reporter: Reynold Xin
> Assignee: Yin Huai
>
> {code}
> scala> hql("describe src").collect().foreach(println)
> [key string None ]
> [value string None ]
> {code}
> The result should contain 3 columns instead of one. This screws up JDBC or
> even the downstream consumer of the Scala/Java/Python APIs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
