Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14712
@wzhfy I am kind of worried about the dependency of Hive metastore.
- Using the same table property names like Hive: Hive metastore could
change them in an unexpected way (for example, by a Hive metastore bug). The
behaviors might be different in different metastore versions. However, the
statistics can be shared by Hive execution and Spark execution. Thus, it could
benefit the Spark users who are using Hive and Spark together on the same set
of tables.
- Using the different names, like what we did for data source table schema:
Spark fully controls them and we just treat the Hive metastore as a persistent
storage of these statistics.
- Provided a configuration parameter so that users can control which option
they preferred?
This is a design decision we need to make. @rxin @yhuai @hvanhovell
@liancheng @cloud-fan @clockfly
---
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
