falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1012) Add support for MapR-FS
Date Tue, 10 Feb 2015 05:20:35 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313592#comment-14313592
] 

Shwetha G S commented on FALCON-1012:
-------------------------------------

ClusterHelper.getNormalisedUrl() has:
{code}
        String normalizedPath = new Path(normalizedUrl + "/").toString();
        return normalizedPath.substring(0, normalizedPath.length() - 1);
{code}
This might be the possible culprit. Check once

nameNode property populated in oozie property is picked up from cluster's write endpoint.
So, if you want namenode to be just maprfs:///, why not set cluster's write endpoint to maprfs:///?
Wouldn't that work?


> 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)

Mime
View raw message