You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Abhishek Agarwal (JIRA)" <ji...@apache.org> on 2014/05/24 23:11:01 UTC
[jira] [Updated] (OOZIE-1856) Show the dataset name along with
coord:latest() in the missing dependencies for coordinator
[ https://issues.apache.org/jira/browse/OOZIE-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhishek Agarwal updated OOZIE-1856:
------------------------------------
Description:
Currently for a coordinator action, which depends on the latest instances of a dataset, missing dependencies are shown something like this
Missing dependencies: ${coord:latestRange(0,0)}\#${coord:latestRange(0,0)}#${coord:latestRange(0,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-3,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-3,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-3,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-34,0)}#${coord:latestRange(-34,0)}#${coord:latestRange(0,0)}#${coord:latestRange(0,0)}
There are around 14 inputs for which the job is waiting on either last available instance or last available 35 instances. It's very difficult to figure out on which input, job is exactly waiting on.
We should show the only those dependencies which could not be resolved and show dataset name in the dependencies.
e.g. ${coord:latestRange(0,0), input1}#${coord:latestRange(0,0), input2}#${coord:latestRange(0,0), input3}#${coord:latestRange(0,0), input4}
was:
Currently for a coordinator action, which depends on the latest instances of a dataset, missing dependencies are shown something like this
Missing dependencies: ${coord:latestRange(0,0)}#${coord:latestRange(0,0)}#${coord:latestRange(0,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-3,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-3,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-3,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-34,0)}#${coord:latestRange(-34,0)}#${coord:latestRange(0,0)}#${coord:latestRange(0,0)}
There are around 14 inputs for which the job is waiting on either last available instance or last available 35 instances. It's very difficult to figure out on which input, job is exactly waiting on.
We should show the only those dependencies which could not be resolved and show dataset name in the dependencies.
e.g. ${coord:latestRange(0,0), input1}#${coord:latestRange(0,0), input2}#${coord:latestRange(0,0), input3}#${coord:latestRange(0,0), input4}
> Show the dataset name along with coord:latest() in the missing dependencies for coordinator
> --------------------------------------------------------------------------------------------
>
> Key: OOZIE-1856
> URL: https://issues.apache.org/jira/browse/OOZIE-1856
> Project: Oozie
> Issue Type: Improvement
> Components: client, coordinator
> Affects Versions: trunk, 3.3.2
> Environment: Oozie server build version: 3.3.2.8
> Oozie client build version:
> Reporter: Abhishek Agarwal
>
> Currently for a coordinator action, which depends on the latest instances of a dataset, missing dependencies are shown something like this
> Missing dependencies: ${coord:latestRange(0,0)}\#${coord:latestRange(0,0)}#${coord:latestRange(0,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-3,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-3,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-3,0)}#${coord:latestRange(0,0)}#${coord:latestRange(-34,0)}#${coord:latestRange(-34,0)}#${coord:latestRange(0,0)}#${coord:latestRange(0,0)}
> There are around 14 inputs for which the job is waiting on either last available instance or last available 35 instances. It's very difficult to figure out on which input, job is exactly waiting on.
> We should show the only those dependencies which could not be resolved and show dataset name in the dependencies.
> e.g. ${coord:latestRange(0,0), input1}#${coord:latestRange(0,0), input2}#${coord:latestRange(0,0), input3}#${coord:latestRange(0,0), input4}
--
This message was sent by Atlassian JIRA
(v6.2#6252)