[
https://issues.apache.org/jira/browse/OOZIE-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000858#comment-17000858
]
Andras Salamon commented on OOZIE-3574:
---------------------------------------
[~zuston] [~matijhs] It seems to me you have found lots of scenarios where
Oozie is not working correctly if we try to use not only HDFS but also S3,
Azure... I think I'll open an umbrella Jira about the cloud improvement and
move all the Jira there as subtasks.
> JavaAction create uncorrect fileSystem instance in addActionLibs method
> -----------------------------------------------------------------------
>
> Key: OOZIE-3574
> URL: https://issues.apache.org/jira/browse/OOZIE-3574
> Project: Oozie
> Issue Type: Bug
> Reporter: Junfan Zhang
> Assignee: Junfan Zhang
> Priority: Major
>
> 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)
