[
https://issues.apache.org/jira/browse/FALCON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308501#comment-14308501
]
Srikanth Sundarrajan commented on FALCON-1012:
----------------------------------------------
{noformat}
org.apache.falcon.FalconException: E0504 : E0504: App directory
[maprfs:/localhost:722/projects/falcon/staging/falcon/workflows/process/oozie-mr-process/ecd4e10f588019c576e38ddeaf28abba_1423056109787/DEFAULT/coordinator.xml]
does not exist
at
org.apache.falcon.workflow.engine.OozieWorkflowEngine.dryRunInternal(OozieWorkflowEngine.java:215)
{noformat}
Error seems to be reported by Oozie. So is there an issue in file creation on
the falcon end or is there an issue within oozie in reading it or is there an
issue in passing the nameNode property value to Oozie ?
> Add support for MapR-FS
> -----------------------
>
> Key: FALCON-1012
> URL: https://issues.apache.org/jira/browse/FALCON-1012
> Project: Falcon
> Issue Type: New Feature
> Components: hadoop, oozie
> Affects Versions: 0.7
> Environment: single node mapr 4.0.1 cluster.
> mapr-oozie 4.0.1
> Reporter: Roman Slysh
> Attachments: falcon.application.log, standalone-cluster.xml
>
>
> Getting error when trying to submit and schedule the oozie process:
> $ bin/falcon entity -submitAndSchedule -type process -file
> examples/entity/filesystem/oozie-mr-process.xml
> Getting wrong conf parameter:
> nameNode=maprfs:/localhost:722
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
