Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/13128#issuecomment-220210997
@yhuai For example, after we starting Spark, we want to do a run-time
configuration change. `set spark.sql.warehouse.dir=x/y/z`. This is not sent to
Hive metastore. Basically, metastore is still using the value we set at the
beginning. See the link:
https://github.com/apache/spark/blob/7bf9b12019bb20470b726a7233d60ce38a9c52cc/sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveSharedState.scala#L39-L48
In addition, I am afraid that `hive.metastore.warehouse.dir` is not the
only parameter users might change at runtime. If any change is made at runtime,
we just change/set the value in our in-memory configuration . We did not
propagate the changes to Hive metastore. Do you think this should be a concern?
If both are not supported, we should issue exceptions to users that the
run-time changes are not supported. Now, we silently accept the Hive-related
configuration changes but the changes are not activated.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
