[
https://issues.apache.org/jira/browse/PIG-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308499#comment-15308499
]
Rohini Palaniswamy commented on PIG-4908:
-----------------------------------------
bq. We shall remove the relative path handling code in a separate ticket,
I think we should be ok to do that. It will have longer path names in the jar
which should not be a problem. Relative path names allow picking up from local
directory when the scripts are part of distributed cache files though. Cannot
think of anything else now, but to be on the safer side will do after this
release.
Committed PIG-4908-3-fixtest.patch to trunk and branch-0.16. Thanks for the
review [~daijy] and [~knoguchi].
> JythonFunction refers to Oozie launcher script absolute path
> ------------------------------------------------------------
>
> Key: PIG-4908
> URL: https://issues.apache.org/jira/browse/PIG-4908
> Project: Pig
> Issue Type: Bug
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: 0.16.0
>
> Attachments: PIG-4908-1.patch, PIG-4908-2-fixtest.patch,
> PIG-4908-3-fixtest.patch
>
>
> We had a scenario where a user had multiple udfs all named udfs.py.
> JythonFunction was referring to the absolute localized path of udfs.py in the
> Oozie launcher. Tasks which ran on a node and which had a different version
> of udfs.py localized to same path (hashcode conflict) as the Oozie launcher
> failed. We should be referring to relative path of the files. The current
> code check is the canonical path starts with cwd, but that does not work as
> the files are downloaded to a different location and symlinked to the current
> working directory of the task attempt.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
