Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/12460#issuecomment-215115938
@dilipbiswal One purpose of re-implementing all DDL as native Spark SQL
command is to minimize dependency to Hive so that we can move Hive into a
separate data source some day. That said, we really don't want to make these
new DDL commands rely on classes like `HiveClient`, `HiveClientImpl`, or
`HiveSessionCatalog`. When you need to access Hive table metadata, you should
access them via `CatalogTable` rather than depending on any Hive data structure.
---
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
