Github user ericl commented on the issue:
https://github.com/apache/spark/pull/16514
I see. What do you think about adding that check in the caching code rather
than require invalidation calls?
After all, the SET LOCATION may be issued by a separate Spark cluster
connecting to the same hive metastore, so you'd need to invalidate all the
cache of all clients talking to the metastore.
---
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
