[
https://issues.apache.org/jira/browse/OOZIE-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021860#comment-17021860
]
Andras Salamon commented on OOZIE-3574:
---------------------------------------
I've tried to apply the latest patch locally and got the following error
message:
{noformat}
error: patch failed:
core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java:18
error:
core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java:
patch does not apply
{noformat}
[~zuston] Can you please rebase it on top of the current master (OOZIE-3575
also changed {{JavaActionExecutor a week ago)}}.
> JavaAction create incorrect fileSystem instance in addActionLibs method
> -----------------------------------------------------------------------
>
> Key: OOZIE-3574
> URL: https://issues.apache.org/jira/browse/OOZIE-3574
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Junfan Zhang
> Assignee: Junfan Zhang
> Priority: Major
> Attachments: OOZIE-3574-v1.patch, OOZIE-3574-v2.patch,
> OOZIE-3574-v3.patch
>
>
> Code is
> [here|https://github.com/apache/oozie/blob/9c288fe5cea6f2fbbae76f720b9e215acdd07709/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L734].
> If actionlibPath scheme is different from appPath (like actionLibPath's
> scheme is s3a, but the appPath is hdfs), this will fail to execute
> {{fs.exist(actionLibsPath)}}. So i think Oozie should create fileSystem by
> actionLibsPath.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
