RussellSpitzer commented on issue #2972: URL: https://github.com/apache/iceberg/issues/2972#issuecomment-912996622
For any future readers, this is unpatchable on Spark 3.0 (3.1 + are fine once the above pr is merged). The underlying issue there is prior to [SPARK-32990](https://issues.apache.org/jira/browse/SPARK-32990) the V1 SparkSession catalog refresh method is called whenever `REFRESH TABLE` is invoked. This means we can't change the behavior of the refresh table command. A workaround is too instead use ```cloneSession()``` on the `SparkSession` class and discard the previous session. This will recreate the catalog and pick up new Iceberg Table changes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
