Reverted pulsar version to 3.2.2 while fixing avro vulnerability #164
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
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.
To address the AVRO vulnerability, PR#165 was merged into the master branch, and PR#161 was merged into the branch-6.0. The changes on master branch upgraded the Pulsar version to 3.3.2, which includes the FeatureNotSupportedException class, a class that is not present in earlier versions.
However, in the spring-example application, there are dependency discrepancies. While pulsar-client-original is upgraded to 3.3.2, some of its nested modules are still on version 3.2.3, which lacks the FeatureNotSupportedException class.
Additionally, with the changes introduced in PR#163, which disables PulsarAdmin creation, another error is triggered—ClassNotFoundException. This occurs because the FeatureNotSupportedException class is missing in Pulsar 3.2.3.
Rolling back to an older version of Pulsar & fixing avro vulnerability just like PR#161 resolves the issue.
Once the migration from javax to Jakarta in Pulsar is complete, this problem should no longer occur.