You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Pallavi Rao (JIRA)" <ji...@apache.org> on 2016/08/05 04:27:20 UTC
[jira] [Resolved] (FALCON-2039) Move falcon post processing to
falcon server and remove post processing action from falcon workflow
[ https://issues.apache.org/jira/browse/FALCON-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pallavi Rao resolved FALCON-2039.
---------------------------------
Resolution: Fixed
Fix Version/s: trunk
Issue resolved by pull request 244
[https://github.com/apache/falcon/pull/244]
> Move falcon post processing to falcon server and remove post processing action from falcon workflow
> ---------------------------------------------------------------------------------------------------
>
> Key: FALCON-2039
> URL: https://issues.apache.org/jira/browse/FALCON-2039
> Project: Falcon
> Issue Type: Improvement
> Reporter: sandeep samudrala
> Assignee: Praveen Adlakha
> Fix For: trunk
>
>
> Move falcon post processing to falcon server and remove post processing action from falcon workflow.
> Currently challenges with post-processing.
> 1) In case of post processing failures, the workflow status goes into killed/failed.
> 2) Extra container being wasted for post processing action in the workflow, which can be avoided if it can be moved to falcon server itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)