[SPARK-16471] [SQL] Remove Hive-specific CreateHiveTableAsSelectLogicalPlan [WIP] #14123
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?
CreateHiveTableAsSelectLogicalPlanis a Hive-specific logical node. This is not a good design. We need to consolidate it withCreateTableUsingAsSelectto build a unified logical nodeCreateTableAsSelect.The first step is to make more general the signature of
CreateTableUsingAsSelectby usingCatalogTableas the input of Table metadata. The logical node is renamed toCreateTableAsSelect. The new interface will be likeThe second step is to convert
CreateHiveTableAsSelectLogicalPlanintoCreateTableAsSelect.This PR is based on the compare of the two interfaces. The details are described below.
Currently, the SQL interface is the only only entrance to
CreateHiveTableAsSelectLogicalPlan. Below describes the correspondence between the SQL interface andCreateHiveTableAsSelectLogicalPlanCreateTableUsingAsSelecthas three entrances. Below is the the correspondence:How was this patch tested?
The existing test cases cover the code refactoring