-
Couldn't load subscription status.
- Fork 4.8k
HIVE-29238:upgrade kafka version to fix CVE-2024-31141 and CVE-2021-3… #6110
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
base: master
Are you sure you want to change the base?
Conversation
| <junit.jupiter.version>5.13.3</junit.jupiter.version> | ||
| <junit.vintage.version>5.13.3</junit.vintage.version> | ||
| <kafka.version>2.5.0</kafka.version> | ||
| <kafka.version>3.9.1</kafka.version> |
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.
If I recall well there were issues with previous upgrade attempts. Please check the (git) history and related PRs for more information to ensure that code remains functional.
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.
yes I am aware of that, its wip right now, I am planning to address those issues if I get a grren label in current state
|
earlier kafka upgrade was made for the sake of compatibility needed as mentioned in #4082 and this was reverted because some test cases were disabled to check upgrade properly and this was not an issue anymore due to refractor as mentioned in this revert ticket https://issues.apache.org/jira/browse/HIVE-27475 and after that a flaky test related to it was enabled int this ticket https://issues.apache.org/jira/browse/HIVE-27502 and it is also passing regularly locally after the upgrade. |
|
|
most changes proposed are in accordance to following changes in kafka dependency: https://github.com/apache/kafka/pull/12590/files |



…8153
What changes were proposed in this pull request?
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?