[ https://issues.apache.org/jira/browse/OOZIE-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16445954#comment-16445954 ]
Andras Piros commented on OOZIE-1624: ------------------------------------- Thanks [~matijhs]! Now I see the value of this JIRA in its entirety. Commented on the review request a few items. [~gezapeti] [~kmarton] what is your opinion about: * whether we should look at the whole sharelib path (Rohini's take) instead of parent directory name and / or file name only (Puru's take) * whether we should have a preconfigured blacklist which JAR patterns we should never allow to exclude, e.g. {{oozie*.jar}} Imagine following sharelib contents: * {{pig/lib/jackson*.jar}} * {{hbase/lib/jackson*.jar}} * {{oozie/jackson*.jar}} * user provided {{jackson*.jar}} As a user I want following distinct use cases: * exclude {{pig/lib/jackson*.jar}} only * exclude {{pig/lib/jackson*.jar}} and {{hbase/lib/jackson*.jar}} * exclude {{pig/lib/jackson*.jar}}, {{hbase/lib/jackson*.jar}}, and {{oozie/jackson*.jar}} * exclude everything which is {{jackson*.jar}}, independent of location > Exclusion pattern for sharelib JARs > ----------------------------------- > > Key: OOZIE-1624 > URL: https://issues.apache.org/jira/browse/OOZIE-1624 > Project: Oozie > Issue Type: Sub-task > Affects Versions: 4.3.1 > Reporter: Purshotam Shah > Assignee: Purshotam Shah > Priority: Major > Attachments: OOZIE-1624-V2.patch, OOZIE-1624-V3.patch, > OOZIE-1624-V4.patch, OOZIE-1624-v1.patch > > > Sharelib may bring some jar which might conflict with user jars. > Ex. Sharelib hive has json-2.xxxx.jar, where as some of the user use-case > need higher version of json jar. > He should be able to exclude sharelib json jar and bring his own version. > <property> > <name>oozie.action.sharelib.for.hive.exclusion</name> > <value>json-\*.jar|abc-*.jar</value> > </property> -- This message was sent by Atlassian JIRA (v7.6.3#76005)