HIVE-25813: Create Table x Like commands based storage handlers fail … #3301
Conversation
This file contains 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
kgyrtkirk
added
tests pending
tests unstable
and removed
tests failed
tests pending
labels
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…over is fixed
What changes were proposed in this pull request?
CTLT commands based on external tables will not copy over table properties of the source table.
Why are the changes needed?
Because it is consistent with other Query engines like MySql and Redshift.
Does this PR introduce any user-facing change?
Yes, When users execute CREATE TABLE x LIKE command, we'll no more copy the table properties of source table to the destination table, we'll only copy the table/column schema of the source table.
How was this patch tested?
Local machine, Unit tests