[SPARK-54216][SQL] Add regression tests for V2 table cache refresh with immutable Table instances#55416
Draft
yadavay-amzn wants to merge 1 commit intoapache:masterfrom
Draft
Conversation
…th immutable Table instances Add tests verifying that refreshTable() and recacheByPlan() return fresh data for DataSource V2 tables with immutable Table instances (copyOnLoad=true). The underlying issue was fixed by SPARK-54387 and SPARK-54424, which introduced tryRefreshPlan to reload table metadata from the catalog before re-caching. These tests serve as explicit regression coverage for the scenario described in SPARK-54216.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Add regression tests verifying that
refreshTable()andrecacheByPlan()return fresh data for DataSource V2 tables with immutable Table instances (copyOnLoad=true).Why are the changes needed?
SPARK-54216 describes a bug where cached V2 table queries return stale data after
refreshTable(). Investigation shows the underlying issue was already fixed by:V2TableRefreshUtil.refresh()before re-executing cached planstryRefreshPlanandtryRebuildCacheEntryfor better error handlingHowever, there were no explicit regression tests for the exact scenario described in SPARK-54216. These tests serve as coverage for that scenario.
Does this PR introduce any user-facing change?
No (test-only).
How was this patch tested?
Two new tests in
CachedTableSuite:refreshTable should return fresh data for V2 tables with immutable Table- testsCACHE TABLE+INSERT+refreshTableflowrecacheByPlan should return fresh data for V2 tables- testsDataFrame.cache()+INSERT+recacheByPlanflowBoth tests pass on current master.
Was this patch authored or co-authored using generative AI tooling?
Yes