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

["Purshotam Shah (JIRA)" <ji...@apache.org>]

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

Purshotam Shah commented on OOZIE-1624:
---------------------------------------

{quote}
Even with metafile, the shareliblist command exposes the file paths. hbase. *thrift. *. jar would match both cases. It is easy to write a generic regex for a file under given directory how many ever levels it is nested.
{quote}
This is what my worry is, full path is exposed to user and he create any regex which might break in future release. Not every user will follow best practices.
Ex 1.
Pig_current/Pig can internally point to .../pig.10.0.1.0.xxxxxx/lib/jar
Since path is exposed to user, he can create regex as .*/pig.10.0.1.0.xxxxxx/lib/jar/abc*.jar.
If we move pig_current/pig to next pig release, then all user job at production will start failing.

Ex 2.
Currently if thift jar in in hbase dir, habse/lib/thift.jar
By looking at sharelib full path, user can create regex as .*/hbase/lib/thift.jar.
This will prohibit ops/admin to change hbase sharelib directory structure.

> Exclusion pattern for sharelib.
> -------------------------------
>
>                 Key: OOZIE-1624
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1624
>             Project: Oozie
>          Issue Type: Sub-task
>            Reporter: Purshotam Shah
>            Assignee: Purshotam Shah
>         Attachments: OOZIE-1624-V2.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
(v6.3.4#6332)