Relax Hive-3 column datatype changes #161
Merged
Conversation
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
This would make Hive 2 and Hive 3 to have similar restriction for column type changes.
Member
Author
|
This run confirms that it works for hive3 when we remove the commented coercions. Waiting for PTs |
Member
Author
|
For the non-kerberized tests it works - so I guess the change works as expected. |
ebyhr
approved these changes
Feb 1, 2023
Member
Author
|
Updated the hive-site for kerberized hive. Coercion tests were running fine. |
kokosing
approved these changes
Feb 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This would make Hive 2 and Hive 3 to have similar restriction for column type changes.
In case of hive2 - the default value of an equivalent property hive.metastore.disallow.incompatible.col.type.changes is false.
Preparatory PR for trinodb/trino#15898