[
https://issues.apache.org/jira/browse/OOZIE-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000821#comment-17000821
]
Junfan Zhang commented on OOZIE-3574:
-------------------------------------
[~matijhs] Thanks your response. I will recheck the patch and upload it.
In addition, Why I found this problem, because we use aws {{S3}} to store
workflow xml, but {{Oozie}} sharelib related files are still stored in
{{HDFS}}. I found that Oozie cannot support this scenario, so I modified the
current Oozie code. If there is such a demand, can we open another jira to
solve this problem, how do you think? [~asalamon74].
*The problems we encountered are as follows:*
When the workflow xml address has no scheme and uses the s3a protocol by
default, {{Oozie}} is required to provide optional parameters to support
reading the workflow xml path from {{S3A}} instead of {{HDFS}}
> 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)
