[ https://issues.apache.org/jira/browse/OOZIE-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040902#comment-16040902 ]
ASF GitHub Bot commented on OOZIE-2929: --------------------------------------- GitHub user todaychi opened a pull request: https://github.com/apache/oozie/pull/31 make sla variables can be resolved https://issues.apache.org/jira/browse/OOZIE-2929 You can merge this pull request into a Git repository by running: $ git pull https://github.com/todaychi/oozie master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/oozie/pull/31.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #31 ---- ---- > 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)