[SPARK-33815][SQL] Migrate ALTER TABLE ... SET [SERDE|SERDEPROPERTIES] to use UnresolvedTable to resolve the identifier #30813
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?
This PR proposes to migrate
ALTER TABLE ... SET [SERDE|SERDEPROPERTIESto useUnresolvedTableto resolve the table identifier. This allows consistent resolution rules (temp view first, etc.) to be applied for both v1/v2 commands. More info about the consistent resolution rule proposal can be found in JIRA or proposal doc.Note that
ALTER TABLE ... SET [SERDE|SERDEPROPERTIES]is not supported for v2 tables.Why are the changes needed?
The PR makes the resolution consistent behavior consistent. For example,
, but after this PR:
, which is the consistent behavior with other commands.
Does this PR introduce any user-facing change?
After this PR,
tin the above example is resolved to a temp view first instead ofspark_catalog.test.t.How was this patch tested?
Updated existing tests.