You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Chi Wen (JIRA)" <ji...@apache.org> on 2017/06/07 13:42:18 UTC
[jira] [Updated] (OOZIE-2929) Coordinator SLA should support
configuration variable
[ https://issues.apache.org/jira/browse/OOZIE-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chi Wen updated OOZIE-2929:
---------------------------
Attachment: OOZIE-2929-001.patch
> Coordinator SLA should support configuration variable
> -----------------------------------------------------
>
> Key: OOZIE-2929
> URL: https://issues.apache.org/jira/browse/OOZIE-2929
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Reporter: Chi Wen
> Attachments: OOZIE-2929-001.patch
>
>
> if coordinator.xml define SLA like this:
> <sla:info>
> <sla:nominal-time>${nominal_time}</sla:nominal-time>
> <sla:should-end>${ 1 * HOURS}</sla:should-end>
> <sla:max-duration>${1 * MINUTES}</sla:max-duration>
> </sla:info>
> In job.properties define: nominal_time=${coord:nominalTime()}
> Then coordinator will run failed for "Coord Job Materialization Error: Could not parse [${coord:nominalTime()}] using [yyyy-MM-dd'T'HH:mm+0800] mask";
> Oozie should support use define a variable for SLA;
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)