You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Abhishek Bafna (JIRA)" <ji...@apache.org> on 2016/09/15 18:27:20 UTC
[jira] [Commented] (OOZIE-2569) Adding yarn-site, core-site,
hdfs-site and mapred-site into spark launcher
[ https://issues.apache.org/jira/browse/OOZIE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15494155#comment-15494155 ]
Abhishek Bafna commented on OOZIE-2569:
---------------------------------------
Ping: [~rkanter], [~jaydeepvishwakarma]
> Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher
> ---------------------------------------------------------------------------
>
> Key: OOZIE-2569
> URL: https://issues.apache.org/jira/browse/OOZIE-2569
> Project: Oozie
> Issue Type: Bug
> Components: core
> Reporter: Abhishek Bafna
> Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2569-00.patch, OOZIE-2569-02.patch, OOZIE-2569-03.patch
>
>
> Oozie Spark action requires yarn-site, core-site, hdfs-site and mapred-site to be present in the classpath for launching the spark applications. Currently we manually copy these files into oozie spark sharelib.
> Until it is fixed through the spark, we can copy the {{oozie.action.conf.xml}} file as yarn-site, core-site, hdfs-site and mapred-site, which will avoid manual steps of copying those files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)