falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shaik Idris Ali (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (FALCON-384) Support oozie coord reruns based on argument in Falcon
Date Tue, 30 Sep 2014 14:10:34 GMT

     [ https://issues.apache.org/jira/browse/FALCON-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Shaik Idris Ali reassigned FALCON-384:

    Assignee: Shaik Idris Ali

> Support oozie coord reruns based on argument in Falcon
> ------------------------------------------------------
>                 Key: FALCON-384
>                 URL: https://issues.apache.org/jira/browse/FALCON-384
>             Project: Falcon
>          Issue Type: Bug
>          Components: oozie
>            Reporter: Shaik Idris Ali
>            Assignee: Shaik Idris Ali
> Currently, when falcon instance is rerun, we check if the workflow for given instance
is present and just use oozie's workflow rerun.
> However users might need coord reruns instead of workflow reruns,
> 1. Users may want to change job conf (hadoop conf) etc, with workflow reruns, exactly
the same hadoop job is retried, but with coord rerun a new workflow instance is created with
> 2. Users might use EL expressions like latest(0), which should be resolved again with
new set of datasets.
> 3. Users might also need to re-evaluate dependencies in cases we have chain of jobs.
With just workflow rerun the job simply kicks-off without checking for data.
> Provide option like refresh and invoke coord rerun with refresh.

This message was sent by Atlassian JIRA

View raw message