rangareddy commented on issue #17217: URL: https://github.com/apache/hudi/issues/17217#issuecomment-5366108828
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-2699). **Findings: probably resolved, but the definitive check needs a built bundle rather than a source grep.** I found no zookeeper dependency carrying a **tests classifier** anywhere in the poms on `master`. What remains: - `hudi-client/hudi-spark-client/pom.xml:169-173` - a plain `org.apache.zookeeper:zookeeper` with `<scope>test</scope>`. That is a test-scoped dependency, not a tests-classifier artifact, so it should not reach a shaded bundle. - `hudi-sync/hudi-adb-sync/pom.xml:68-71` and `hudi-utilities/pom.xml:307-311` - zookeeper listed as `<exclusion>`s. - Three bundle poms mention zookeeper at all: `packaging/hudi-integ-test-bundle`, `packaging/hudi-spark-bundle` and `packaging/hudi-utilities-bundle`. So the specific artifact described here looks gone. I am not closing it on that basis, though, because a shaded bundle's contents come from the shade plugin's include set plus transitive resolution - not from what a pom grep shows. The authoritative check is to build a bundle and run `jar tf` on it looking for zookeeper test classes. That check is cheap and would settle this definitively. Recommend running it and closing if clean. -- 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]
