falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-635) Add recipe option in falcon client
Date Thu, 04 Sep 2014 06:05:51 GMT

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

Srikanth Sundarrajan commented on FALCON-635:
---------------------------------------------

* Does falcon server understand what a recipe is or is it simply a client magic ?
* Once scheduled, how does the user track the execution & manage it ? 
* Is the property file spec specific to a recipe or generic ?
* Is the recipe hosted in the server or in some shared directory?

Would help if this is detailed (both user docs and design notes) in some place (possibly in
docs as [~svenkat] has already pointed out).


> Add recipe option in falcon client
> ----------------------------------
>
>                 Key: FALCON-635
>                 URL: https://issues.apache.org/jira/browse/FALCON-635
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: client
>    Affects Versions: 0.6
>            Reporter: Venkatesh Seetharam
>            Assignee: Sowmya Ramesh
>              Labels: recipes
>         Attachments: FALCON-635.patch
>
>
> CLI accepts recipe option with a properties file and does the following:
> * looks for a specific recipe in the recipe home
> * Invokes a Tool to substitute the properties in the templated process for the recipe
(Falcon provides a base tool that recipes can override)
> * Validates the properties file provided by the user
> * optionally copy the artifacts to HDFS
> *  validate the generated entity
> * submit and schedule this entity



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

Mime
View raw message