You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org> on 2015/02/13 02:55:12 UTC

[jira] [Commented] (FALCON-1023) Missing Features in Falcon that are available to Oozie

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

Srikanth Sundarrajan commented on FALCON-1023:
----------------------------------------------

Thanks for bringing this up, we can attempt to include in the next release.

> Missing Features in Falcon that are available to Oozie
> ------------------------------------------------------
>
>                 Key: FALCON-1023
>                 URL: https://issues.apache.org/jira/browse/FALCON-1023
>             Project: Falcon
>          Issue Type: Improvement
>          Components: oozie
>    Affects Versions: 0.6
>         Environment: Falcon Improvements
>            Reporter: Thirumalai Varadarajan
>             Fix For: 0.7
>
>
> Hi,
> We are trying to replace our existing oozie workflows with falcon. But then we are facing few issues with falcon which is a roadblock for us to move from Oozie to Falcon. Apart from that Falcon has everything which a Oozie can do. Here are few of our findings:
> 1. In Oozie workflows we call a shell script and with the values we get from our scripts (like timestamp, date, latest folder, partition and many more) we retrieve those values using ${wf:actionData('<SCRIPT NAME>')['<VALUE ECHOED FROM SHELL SCRIPT>']} command and then pass them to subsequent pig scripts or hive or MRs. 
> 2. Please bring in different actions in Falcon for mailing and more features in Oozie so that Falcon can completely replace Oozie. 



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