Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/13156#discussion_r63729506
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/MetastoreDataSourcesSuite.scala
---
@@ -622,7 +622,7 @@ class MetastoreDataSourcesSuite extends QueryTest with
SQLTestUtils with TestHiv
.mode(SaveMode.Append)
.saveAsTable("arrayInParquet")
- sessionState.refreshTable("arrayInParquet")
+ sparkSession.catalog.refreshTable("arrayInParquet")
--- End diff --
Actually, invalidateTable and refreshTable do have different meanings. The
current implementation of `HiveMetastoreCatalog.refreshTable` is
`HiveMetastoreCatalog.invalidateTable` (and then we retrieve the new metadata
lazily). But, it does not mean that `refreshTable` and `invalidateTable` have
the same semantic. If we should remove any of `invalidateTable` or
`refreshTable` should be discussed in a different thread.
---
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]
