[
https://issues.apache.org/jira/browse/OOZIE-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387452#comment-14387452
]
Rohini Palaniswamy commented on OOZIE-1624:
-------------------------------------------
bq. With recent change in sharelib, we will never have duplicate files added to
distributed cache. User should be agnostic to sharelib path and it can change.
Those duplicates are only by file names and file size and checksum is not
checked and sometimes that can be a problem. We should exclude before checking
for duplicates. I think that is what is being done now, just that it has to be
on the full path instead of the file name. For eg: If both hbase and hive had a
thrift.jar in sharelib, setting .*/hbase*/thrift.jar should make put the hive
thrift.jar. If thrift.jar has to be totally excluded then .*thrift*.jar can be
specified.
> 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)
