[
https://issues.apache.org/jira/browse/OOZIE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236823#comment-13236823
]
Maxime Petazzoni commented on OOZIE-778:
----------------------------------------
I second this. It would be nice if Oozie was able to support a "NOW" start
time, adjusted to a configurable, "nearest" time. Something like:
* ${coord:now(15)} would have the first materialization of the coordinator at
the next 15min increment of the hour: submitting at 4:23pm for example would
see the first materialization at 4:30pm.
* ${coord:now(1)} would be at the end of the current minute (submitting at
4:23:xx pm -> 4:24:00).
> Support default or EL function for coordinator start time
> ---------------------------------------------------------
>
> Key: OOZIE-778
> URL: https://issues.apache.org/jira/browse/OOZIE-778
> Project: Oozie
> Issue Type: Improvement
> Reporter: Mohammad Kamrul Islam
>
> Currently start time needs to be defined statically.
> There are two additional ways, this could be made flexible.
> 1. By default, current time/NOW will be assumed, if it is not assigned.
> 2. Provide am EL function to define the current(any) time in specific format.
> For option 1: The open question is till what granular the current time should
> be considered. It is in minute or second or nearest hour or nearest 5 minute.
> for example, current time is 05:01:23, what should be the default: is it
> 05:01:00/05:00:00/05:01:23?
> For option 2: it could be like currentTime(<formatString>)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
