[SPARK-34027][SPARK-34213][SQL][FOLLOWUP][DOCS] Update the SQL migration guide about table re-caching
### What changes were proposed in this pull request? This is a follow up of the PRs https://github.com/apache/spark/pull/31066 and https://github.com/apache/spark/pull/31304 that changed behavior of some commands regarding to table cache refreshing. The PR updates the SQL migration guide, in particular, the item which describes new behavior. ### Why are the changes needed? To inform users about command behavior changes. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? N/A Closes #31309 from MaxGekk/refreshTable-sql-migration-guide. Authored-by: Max Gekk <max.gekk@gmail.com> Signed-off-by: Dongjoon Hyun <dhyun@apple.com>
This commit is contained in:
parent
ab6c0e5d10
commit
652bdf0d5a
|
@ -45,6 +45,9 @@ license: |
|
|||
* `ALTER TABLE .. ADD PARTITION`
|
||||
* `ALTER TABLE .. RENAME PARTITION`
|
||||
* `ALTER TABLE .. DROP PARTITION`
|
||||
* `ALTER TABLE .. RECOVER PARTITIONS`
|
||||
* `MSCK REPAIR TABLE`
|
||||
* `LOAD DATA`
|
||||
* `REFRESH TABLE`
|
||||
* and the method `spark.catalog.refreshTable`
|
||||
In Spark 3.1 and earlier, table refreshing leaves dependents uncached.
|
||||
|
|
Loading…
Reference in a new issue