dybyte opened a new pull request, #9632: URL: https://github.com/apache/seatunnel/pull/9632
Fixes https://github.com/apache/seatunnel/issues/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](https://github.com/apache/seatunnel/issues/9509) ### Does this PR introduce _any_ user-facing change? no ### How was this patch tested? Covered by existing tests. ```java if (container instanceof Spark3Container) { log.info("Skip on Spark 3.3.0 due to Netty conflict."); return; } ``` Since the underlying Netty conflict has been resolved in this patch, this workaround has been removed, and the MaxCompute sink e2e test now runs and passes successfully on Spark 3.3.0. ### Check list * [ ] If any new Jar binary package adding in your PR, please add License Notice according [New License Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/contribution/new-license.md) * [ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs * [ ] If you are contributing the connector code, please check that the following files are updated: 1. Update [plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties) and add new connector information in it 2. Update the pom file of [seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml) 3. Add ci label in [label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml) 4. Add e2e testcase in [seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/) 5. Update connector [plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
