-
Couldn't load subscription status.
- Fork 28.9k
[SPARK-29069][SQL] ResolveInsertInto should not do table lookup #25774
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| } | ||
| v2TableOpt.map(DataSourceV2Relation.create).getOrElse(u) | ||
|
|
||
| case i @ InsertIntoStatement(u: UnresolvedRelation, _, _, _, _) if i.query.resolved => |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
simpler to ResolveRelations, ResolveTables should handle both UnresolvedRelation and InsertIntoStatement(UnresolvedRelation, ...).
| case _ => | ||
| i | ||
| case i @ InsertIntoStatement(r: DataSourceV2Relation, _, _, _, _) if i.query.resolved => | ||
| // ifPartitionNotExists is append with validation, but validation is not supported |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just indentation changes.
|
Test build #110518 has finished for PR 25774 at commit
|
|
retest this please |
|
Test build #110547 has finished for PR 25774 at commit
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Merged to master. |
|
Late +1 |
What changes were proposed in this pull request?
It's more clear to only do table lookup in
ResolveTablesrule (for v2 tables) andResolveRelationsrule (for v1 tables).ResolveInsertIntoshould only resolve theInsertIntoStatementwith resolved relations.Why are the changes needed?
to make the code simpler
Does this PR introduce any user-facing change?
no
How was this patch tested?
existing tests