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-637) Add packaging for recipes
Date Tue, 17 Feb 2015 23:51:13 GMT

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

Sowmya Ramesh commented on FALCON-637:

Each recipe and its dependencies is packaged into jar and then all the recipes into a uber
jar file that can be distributed. 
Recipes provided by Falcon will be packaged and will be at the $FALCON_HOME path.

For the recipes provided out of the box, deploying them when Falcon service starts up is an
option. It is not an feasible solution as it requires Falcon to be restarted in case if recipe
artifacts have to be updated or new recipe has to be deployed.

Recipe should provide deploy and update options for the recipe artifacts deployment.
For manual Installation of Falcon user has to do deployment manually.

For HDP, installer can deploy the recipes and then update the startup.properties with the
path which will be used for list and describe operations.

For V1 user is allowed to deploy the recipe only on HDFS and local FS support can be added
as an improvement later.

> Add packaging for recipes
> -------------------------
>                 Key: FALCON-637
>                 URL: https://issues.apache.org/jira/browse/FALCON-637
>             Project: Falcon
>          Issue Type: Sub-task
>    Affects Versions: 0.6
>            Reporter: Venkatesh Seetharam
>            Assignee: Sowmya Ramesh
>              Labels: recipes
> * package each recipe and its dependencies into a uber jar or a tar
> * We need to have a superpom for recipes that packages all the recipes into a uber tar
file that can be distributed

This message was sent by Atlassian JIRA

View raw message