Skip to content

Conversation

@ramitg254
Copy link
Contributor

…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?

<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>
Copy link
Member

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.

Copy link
Contributor Author

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

@ramitg254 ramitg254 changed the title [WIP]HIVE-29238:upgrade kafka version to fix CVE-2024-31141 and CVE-2021-3… HIVE-29238:upgrade kafka version to fix CVE-2024-31141 and CVE-2021-3… Oct 24, 2025
@ramitg254
Copy link
Contributor Author

ramitg254 commented Oct 24, 2025

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.
@zabetak @kokila-19 can you please review this.

Copy link
Member

@zabetak zabetak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before merging this PR we should ensure that kafka_storage_handler.q runs fine so addressing https://issues.apache.org/jira/browse/HIVE-23985 seems like a prerequisite for merging this PR. I will start a flaky check for kafka_storage_handler.q in master and if it passes I will reenable the test.

In the meantime, you can run the test locally and check if it passes with the changes in this PR.

@ramitg254
Copy link
Contributor Author

Before merging this PR we should ensure that kafka_storage_handler.q runs fine so addressing https://issues.apache.org/jira/browse/HIVE-23985 seems like a prerequisite for merging this PR. I will start a flaky check for kafka_storage_handler.q in master and if it passes I will reenable the test.

In the meantime, you can run the test locally and check if it passes with the changes in this PR.

with the current changes I am seeing errors while running this test so trying to solve those errors in the meantime

@zabetak
Copy link
Member

zabetak commented Nov 7, 2025

@ramitg254 Please take a look at the PR for https://issues.apache.org/jira/browse/HIVE-27407. In the past I fixes some of these errors there.

@ramitg254
Copy link
Contributor Author

@zabetak Thanks for the info, some props changes were left , I have added those changes and enabled the kafka_storage_handler.q and results are getting generated so its fine now.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Nov 8, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants