PandaMonkey created OOZIE-3185:
----------------------------------
Summary: Conflicting JARs org.apache.derby exist in Oozie
Key: OOZIE-3185
URL: https://issues.apache.org/jira/browse/OOZIE-3185
Project: Oozie
Issue Type: Bug
Components: core
Affects Versions: 5.0.0b1
Reporter: PandaMonkey
Fix For: 5.0.0
Attachments: oozie.txt
Hi, by analyzing oozie-master\core\pom.xml, I found that there are two versions
of org.apache.derby:derby. Their introduced path is:
1.
org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.derby:derby:10.10.1.1::compile
2.
org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.hive:hive-exec:1.2.0:core:compile->org.apache.hive:hive-metastore:1.2.0::compile->org.apache.derby:derby:10.11.1.1::compile
Of them, org.apache.derby:derby:10.10.1.1 is the transitively introduced by
org.apache.hive:hive-exec and org.apache.derby:derby:10.11.1.1 is the direct
dependency. By further analyzing the source code, *we found they have too many
different features*.
Also, I found that you have already gave derby a exclusion tag when
transitively introducing derby by hive-beeline to avoid dependency conflict.
So it would be nice to keep the consistency of library version for the project
long-term health, maybe update org.apache.derby:derby from 10.10.1.1 to
10.11.1.1, or exclude derby from hive-exec is a good choice. Hope this can help
you. Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
