[ https://issues.apache.org/jira/browse/SPARK-27248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun resolved SPARK-27248. ----------------------------------- Resolution: Fixed Assignee: William Wong Fix Version/s: 3.0.0 This is resolved via https://github.com/apache/spark/pull/24221 > REFRESH TABLE should recreate cache with same cache name and storage level > -------------------------------------------------------------------------- > > Key: SPARK-27248 > URL: https://issues.apache.org/jira/browse/SPARK-27248 > Project: Spark > Issue Type: Bug > Components: SQL > Affects Versions: 3.0.0 > Reporter: William Wong > Assignee: William Wong > Priority: Major > Fix For: 3.0.0 > > > If we refresh a cached table, the table cache will be first uncached and then > recache (lazily). Currently, the logic is embedded in > CatalogImpl.refreshTable method. > The current implementation does not preserve the cache name and storage > level. As a result, cache name and cache level could be changed after a > REFERSH. IMHO, it is not what a user would expect. > I would like to fix this behavior by first save the cache name and storage > level for recaching the table. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org