Github user mallman commented on a diff in the pull request:
https://github.com/apache/spark/pull/13818#discussion_r69231754
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/InsertIntoHiveTable.scala
---
@@ -298,6 +298,7 @@ case class InsertIntoHiveTable(
// Invalidate the cache.
sqlContext.sharedState.cacheManager.invalidateCache(table)
+
sqlContext.sessionState.catalog.invalidateTable(table.catalogTable.identifier)
--- End diff --
Essentially this is a "callback" to the session catalog to invalidate this
table in the catalog's table cache, because we just appended to the underlying
table data. In the context of a Hive query, the session catalog's table cache
is `HiveMetastoreCatalog.cachedDataSourceTables`. The results of the `INSERT`
will be invisible in the current session until the table is invalidated.
Another way to think about this code is that it's precisely what makes the
following test snippet work:
https://github.com/VideoAmp/spark-public/blob/spark-15968/sql/hive/src/test/scala/org/apache/spark/sql/hive/parquetSuites.scala#L582-L585
Does that answer your question?
---
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
