Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/12460#issuecomment-215195961
@liancheng Thank you for your comment. Actually initially i started with
the idea of serving the describe command solely from `CatalogTable`. I then
realized that `CatalogTable` may not have all the metadata information that is
required for this command. So i have a couple of high level questions:
1. Can we add more fields to CatalogTable ?
* Some example of fields that miss are retention, privileges.
* When we choose "describe extended partition", quite a few details that
are readily available in HivePartition is not present in our
CatalogTablePartition object.
* Another use case is "describe table column_path". This is served by a
call to Hive's deserializer via. Hive.getFieldsFromDeserializer
2. Do we have flexibility on the output of describe command or we need
match hive's output completely ? If so, we can remove the describe-related
tests from `HiveCompatibiltySuite` and add suitable tests in `SQLQuerySuite`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
