You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mate Juhasz (JIRA)" <ji...@apache.org> on 2019/03/27 12:20:00 UTC

[jira] [Updated] (OOZIE-3450) Investigate and clean git sharelib

     [ https://issues.apache.org/jira/browse/OOZIE-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mate Juhasz updated OOZIE-3450:
-------------------------------
    Attachment: OOZIE-3540-v1.patch

> 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
>            Priority: Major
>         Attachments: 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)