[Bug][Connector-V2] NoSuchMethodError caused by Netty version conflict on Spark 3.3.0 #9632
+34
−17
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.
Fixes #9509
Purpose of this pull request
This pull request fixes a Netty version conflict between the version used internally by the MaxCompute connector and the version bundled with Spark 3.3.0. This conflict previously caused a NoSuchMethodError at runtime. For more context and discussion, please refer to issue#9509
Does this PR introduce any user-facing change?
no
How was this patch tested?
Covered by existing tests.
Since the underlying Netty conflict has been resolved in this patch, this workaround has been removed, and the MaxCompute e2e test now runs and passes successfully on Spark 3.3.0.
Check list
New License Guide