falcon-dev mailing list archives

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

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

Sowmya Ramesh commented on FALCON-635:

Does falcon server understand what a recipe is or is it simply a client magic ?
Its client side, no magic but its magical. :-) From falcon server point of view its just another
process entity scheduled.

Once scheduled, how does the user track the execution & manage it ?
As you'd with a regular process entity, name given by the user in the recipe

.bq Is the property file spec specific to a recipe or generic ?
Property file spec depends on use case and hence It is specific for each recipe.

.bq Is the recipe hosted in the server or in some shared directory?
Recipes will be hosted as a add on [addons directory]

Yes, I will be add the documentation.

> 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

View raw message