kkrugler commented on issue #8136:
URL: https://github.com/apache/hudi/issues/8136#issuecomment-1462510643
Hi @BruceKellan,
> Hi kkrugler, I have seen your project code.
>
> Hudi-flink is not directly open to users.
>
> You rely on hudi-flink in your code, so you indirectly depend on
org.apache.hudi:hudi-flink1.16.x:jar and occur class conflict, you can check it
by executing this command:
>
> ```shell
> mvn dependency:tree
> ```
I explicitly exclude `hudi-flink1.16.x` in the pom.xml. If you follow the
steps to reproduce (above), I'm curious what you get with `mvn
dependency:tree`, and mine doesn't show `hudi-flink1.16.x`.
Also see https://github.com/apache/hudi/pull/7651/files, and the Jira issue
it references, for more background on the root cause of the bug.
> Since it is unrealistic and unfriendly for users to sort out the internal
dependency structure, we provide bundle packages, and users only need to rely
on the hudi-flink-bundle-jar. Such as
[hudi-flink1.15-bundle](https://mvnrepository.com/artifact/org.apache.hudi/hudi-flink1.15-bundle/0.13.0).
Unfortunately for workflows with significant dependencies, using the
`hudi-flink-bundle-jar` is unreasonable as it pulls in many additional
dependencies, which leads to version conflicts with multiple jars on the
classpath.
It would be better to have a bundle jar that fully shades all dependencies,
though that would create a very, very large jar.
--
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]
