You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Gabor Arki (Jira)" <ji...@apache.org> on 2020/07/22 16:05:00 UTC
[jira] [Updated] (KYLIN-4656) Guava classpath conflict caused by
kylin-jdbc 3.1.0 jar
[ https://issues.apache.org/jira/browse/KYLIN-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Arki updated KYLIN-4656:
------------------------------
Description:
The newly released kylin-jdbc 3.1.0 jar contains a shaded, non-repackaged version of the Guava library. This is causing class duplication with the original guava jar if it is also on the classpath which results in non-deterministic, runtime errors depending on which version of a certain guava class has been picked up by the class-loader from the 2 versions. Based on the runtime errors of the missing classes and methods, it seems to be a very old version, probably <=14.
Either implement a proper shading with package relocation or rely on transitive dependency, but do not shade non-repackaged versions of libraries.
was:
The newly released kylin-jdbc 3.1.0 jar contains a shaded, non-repackaged version of the Guava library. This is causing class duplications with the original guava jar if it is also on the classpath which results in non-deterministic, runtime errors depending on which version of a certain guava class has been picked up by the classloader from the 2 versions.
Either implement a proper shading with package relocation or rely on transitive dependency, but do not shade non-repackaged versions of libraries.
> Guava classpath conflict caused by kylin-jdbc 3.1.0 jar
> -------------------------------------------------------
>
> Key: KYLIN-4656
> URL: https://issues.apache.org/jira/browse/KYLIN-4656
> Project: Kylin
> Issue Type: Bug
> Components: Driver - JDBC
> Affects Versions: v3.1.0
> Reporter: Gabor Arki
> Priority: Critical
>
> The newly released kylin-jdbc 3.1.0 jar contains a shaded, non-repackaged version of the Guava library. This is causing class duplication with the original guava jar if it is also on the classpath which results in non-deterministic, runtime errors depending on which version of a certain guava class has been picked up by the class-loader from the 2 versions. Based on the runtime errors of the missing classes and methods, it seems to be a very old version, probably <=14.
>
> Either implement a proper shading with package relocation or rely on transitive dependency, but do not shade non-repackaged versions of libraries.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)