Abacn opened a new issue, #32699:
URL: https://github.com/apache/beam/issues/32699

   ### What happened?
   
   The dependency resolution always falls to kafka-client 2.4.1:
   
   run `./gradlew :sdks:java:io:kafka:kafka-100:dependencies`
   
   ```
   runtimeClasspath - Runtime classpath of source set 'main'.
   +--- org.apache.kafka:kafka-clients:1.0.0 -> 2.4.1
   ```
   
   this can be also checked by adding assert to the integration test class 
(#32698), one now see check failed:
   
   ```
   Class org.apache.beam.sdk.io.kafka.KafkaIOIT
   
   classMethod
   org.junit.ComparisonFailure: expected:<[1.0.0]> but was:<[2.4.1]>
        at org.junit.Assert.assertEquals(Assert.java:117)
        at org.junit.Assert.assertEquals(Assert.java:146)
        at org.apache.beam.sdk.io.kafka.KafkaIOIT.setup(KafkaIOIT.java:177)
   ```
   
   this is because in BeamModulePlugin, there is a logic to force to the 
dependency version defined by the plugin:
   
   
https://github.com/apache/beam/blame/bcd785fcdcaa8f8b55ce32bca7a0e552404de0b1/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L1266
   
   
   ### Issue Priority
   
   Priority: 2 (default / most bugs should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [X] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam YAML
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Infrastructure
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
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]

Reply via email to