[
https://issues.apache.org/jira/browse/OOZIE-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804899#comment-16804899
]
Mate Juhasz commented on OOZIE-3450:
------------------------------------
Thanks [~asalamon74] for the testing.
Could you please give the new patch a try as well?
Interesting that each of the sharelib projects are using the oozie-core as a
provided dependency, the only difference is that while most of them just
reffering to static constants in the ActionExecutor-s, sharelib-git's GitMain
tries to call a method in GitActionExecutor$ActionConfVerifier. This method is
the ActionConfVerifier#checkAndGetTrimmed, which only returns an action conf
value, not connecting strongly anywhere, so I moved it to the GitMain class.
> Investigate and clean git sharelib
> ----------------------------------
>
> Key: OOZIE-3450
> URL: https://issues.apache.org/jira/browse/OOZIE-3450
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: trunk
> Reporter: Andras Salamon
> Assignee: Mate Juhasz
> Priority: Major
> Attachments: OOZIE-3450-v2.patch, OOZIE-3540-v1.patch
>
>
> I've checked the number of jars in the Oozie sharelibs and realized that git
> sharelib contains the highest number of jars (203), it's much more than the
> hive (85), pig (67). Not to mention that we have really small sharelibs like
> distcp (3).
> I don't really understand the reason for this, we need to check if we really
> need all the jars here. The huge number of jars make it slower and it's more
> likely that we get strange errors because of jar conflicts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
