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

Srikanth Sundarrajan commented on FALCON-1108:
----------------------------------------------

Quoting from FALCON-634

{quote}
Each recipe then is a directory archive (directory name could be trivially the 
name of the recipe) which has the implementation of RecipeBuilder and all 
required support libraries necessary. 
...
This should essentially download all the build and runtime libraries hosted on 
the path provided by the listing api, pass the arguments to the recipe builder 
and build the falcon process and feed artefacts in the output location or 
optionally schedule in the live system.
{quote}

Essentially this is implying that there is an interface RecipeBuilder, which 
the end user is at liberty to implement and can choose to bundle along with it 
all required libraries. Both the builder as well as the runtime of the cooked 
recipe (a process) can have their own set of library dependencies. This is the 
reason why there could be library conflicts. Also since the implementation of 
RecipeBuilder is user code, running it inside a hosted service isn't all that 
wise.

I think the reason for confusion is because of the original approach, but we 
are proposing to further strengthen it through a more open mechanism 
(RecipeBuilder interface)

{quote}
A recipe is a template of a Falcon process. There are delimiters to identify 
the variables to be processed by Recipe Cooker. e.g. ##valueToBeReplaced##.
{quote}

> Custom recipe processing
> ------------------------
>
>                 Key: FALCON-1108
>                 URL: https://issues.apache.org/jira/browse/FALCON-1108
>             Project: Falcon
>          Issue Type: Sub-task
>    Affects Versions: 0.6
>            Reporter: Sowmya Ramesh
>              Labels: Recipe
>             Fix For: 0.7
>
>
> Custom recipe cooking to be done on the server side in a separate independent 
> process than Falcon process I.e. It runs in a different JVM. For more details 
> refer [FALCON-1107|https://issues.apache.org/jira/browse/FALCON-1107]



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

Reply via email to