[jira] [Commented] (OOZIE-1624) Exclusion pattern for sharelib JARs

["Peter Cseh (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467456#comment-16467456 ] 

Peter Cseh commented on OOZIE-1624:
-----------------------------------

I don't really see the value of a preconfigured blacklisted JAR pattern as there are almost an infinite way to define the equivalent of "oozie*jar" using regex. :) 
We should definitely log out every single jar we're removing though to avoid confusion about missing jars.

I'd prefer Rohini's take and filter against the full path -  excluding the sharelib root - as it's easy to just add a "*/" to the start of the pattern to exclude it from everywhere and it is more flexible than filtering just for filenames.



 

> 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)