Return-Path: 
 <dev-return-16942-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 1DD7718DBA
	for <apmail-falcon-dev-archive@minotaur.apache.org>;
 Thu, 19 Nov 2015 13:52:13 +0000 (UTC)
Received: (qmail 12180 invoked by uid 500); 19 Nov 2015 13:52:13 -0000
Delivered-To: apmail-falcon-dev-archive@falcon.apache.org
Received: (qmail 12140 invoked by uid 500); 19 Nov 2015 13:52:13 -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 12129 invoked by uid 99); 19 Nov 2015 13:52:12 -0000
Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Nov 2015 13:52:12 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org)
 with ESMTP id 6AC4AC081E
	for <dev@falcon.apache.org>; Thu, 19 Nov 2015 13:52:12 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 1.77
X-Spam-Level: *
X-Spam-Status: No, score=1.77 tagged_above=-999 required=6.31
	tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1,
	RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
	T_RP_MATCHES_RCVD=-0.01] autolearn=disabled
Received: from mx1-us-west.apache.org ([10.40.0.8])
	by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new,
 port 10024)
	with ESMTP id 8vjqaQJNl7rA for <dev@falcon.apache.org>;
	Thu, 19 Nov 2015 13:52:11 +0000 (UTC)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with
 SMTP id 8944F20225
	for <dev@falcon.incubator.apache.org>; Thu, 19 Nov 2015 13:52:11 +0000 (UTC)
Received: (qmail 11475 invoked by uid 99); 19 Nov 2015 13:52:11 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Nov 2015 13:52:11 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 3EA7C2C1F73
	for <dev@falcon.incubator.apache.org>; Thu, 19 Nov 2015 13:52:11 +0000 (UTC)
Date: Thu, 19 Nov 2015 13:52:11 +0000 (UTC)
From: "Peeyush Bishnoi (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12910795.1446747661000.122631.1447941131253@Atlassian.JIRA>
In-Reply-To: <JIRA.12910795.1446747661000@Atlassian.JIRA>
References: <JIRA.12910795.1446747661000@Atlassian.JIRA>
 <JIRA.12910795.1446747661369@arcas>
Subject: [jira] [Comment Edited] (FALCON-1588) Need ability to provide the
 path for recipe files in command line
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Peeyush Bishnoi edited comment on FALCON-1588 at 11/19/15 1:51 PM:
-------------------------------------------------------------------

To provide the recipe properties file on command line and invoking the respective recipe for execution, it is also required to have workflow.xml and recipe template in path. To perform this, I have thought of passing the recipe property file as follows:
{code:java}
$ ./bin/falcon recipe -name hdfs-replication -operation HDFS_REPLICATION -properties <recipe properties file path>
{code}

For execution of recipe, if recipe properties file is provided on command line, look for the respective recipe workflow.xml and template file in the directory path where recipe properties file is located. Also users can still execute the recipe by specifying the directory path through falcon.recipe.path=<recipe directory path> in conf/client.properties. To perform this users can copy the recipe's related files from $FALCON_HOME/data-mirroring/hdfs-replication to accessible directory. 

Similar steps can be performed for Hive replication recipe as well.

Please provide thoughts on the above approach.


was (Author: peeyushb):
To provide the recipe properties file on command line and invoking the respective recipe for execution, it is also required to have workflow.xml and recipe template in path. To perform this, I have thought of passing the recipe property file as follows:
{code:java}
$ ./bin/falcon recipe -operation HDFS_REPLICATION -properties recipe.properties:<recipe properties file path>
{code}

For execution of recipe, if recipe.properties file is provided on command line, look for the respective recipe workflow.xml and template file in one of the location on the basis of recipe name:
   a. In the directory path where recipe.properties file is located.
   a. In the $FALCON_HOME/data-mirroring directory.
   b. In the directory path specified through falcon.recipe.path=<recipe directory path>, if specified in conf/client.properties.

Please provide thoughts on the above approach.

> Need ability to provide the path for recipe files in command line
> -----------------------------------------------------------------
>
>                 Key: FALCON-1588
>                 URL: https://issues.apache.org/jira/browse/FALCON-1588
>             Project: Falcon
>          Issue Type: New Feature
>            Reporter: Ajay Yadava
>            Assignee: Peeyush Bishnoi
>
> Currently recipe path option can only be specified through client.properties file. We should add an option to provide path for recipes through command line as well. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)