Return-Path: 
 <dev-return-9735-apmail-falcon-dev-archive=falcon.apache.org@falcon.apache.org>
X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org
Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 00040177C6
	for <apmail-falcon-dev-archive@minotaur.apache.org>;
 Thu,  5 Feb 2015 11:54:56 +0000 (UTC)
Received: (qmail 53085 invoked by uid 500); 5 Feb 2015 11:54:56 -0000
Delivered-To: apmail-falcon-dev-archive@falcon.apache.org
Received: (qmail 53043 invoked by uid 500); 5 Feb 2015 11:54:56 -0000
Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@falcon.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@falcon.apache.org>
List-Post: <mailto:dev@falcon.apache.org>
List-Id: <dev.falcon.apache.org>
Reply-To: dev@falcon.apache.org
Delivered-To: mailing list dev@falcon.apache.org
Received: (qmail 53032 invoked by uid 99); 5 Feb 2015 11:54:56 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Feb 2015 11:54:56 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3)
    by apache.org (qpsmtpd/0.29) with SMTP; Thu, 05 Feb 2015 11:54:55 +0000
Received: (qmail 52684 invoked by uid 99); 5 Feb 2015 11:54:35 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Feb 2015 11:54:35 +0000
Date: Thu, 5 Feb 2015 11:54:35 +0000 (UTC)
From: "Pallavi Rao (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12772366.1423056628000.265579.1423137275030@Atlassian.JIRA>
In-Reply-To: <JIRA.12772366.1423056628000@Atlassian.JIRA>
References: <JIRA.12772366.1423056628000@Atlassian.JIRA>
 <JIRA.12772366.1423056628019@arcas>
Subject: [jira] [Commented] (FALCON-1012) Add support for MapR-FS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Pallavi Rao commented on FALCON-1012:
-------------------------------------

Not exactly. From what I see from the logs and the definition, Oozie variables are to be set slightly differently when using MapR. As [~rslysh] has pointed out, nameNode=maprfs:/localhost:722 is wrong when using MapR and hence the dryrun fails.

Oozie variables should be (as per http://new.spryinc.com/blog/how-mapr-uses-its-own-storage-layer-and-what-means-oozie):
oozie.wf.application.path=maprfs:/<path>
jobTracker=maprfs:///
nameNode=maprfs:///




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