HIVE-27466. (2.3) Remove obsolete reference to category-X JSON license from NOTICE #5147
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
Member
Author
|
cc @sunchao |
asf-ci-hive
added
tests failed
tests pending
and removed
tests pending
tests failed
labels
Member
|
@pan3793 could you rebase this PR? |
Member
Author
|
After rebase, this patch becomes noop, it's already covered by #5148, close then |
Member
Author
|
@sunchao BTW, I took a look at HIVE-27504 (the last one you listed), looks like a little bit of overkill for a maintenance release, and the patch must be tuned because the dependency trees are quite different. |
Member
|
Thanks. I think it should be OK too. It doesn't seem like a blocker. |
Member
Author
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.
What changes were proposed in this pull request?
Backport HIVE-27466 to 2.3.
Why are the changes needed?
apache/spark#45372 (comment)
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
NO
How was this patch tested?
Review