You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:55:09 UTC
[jira] [Created] (OOZIE-244) GH-326: New 'dateAdd' EL function to
enable specifying dataset ranges based on date deltas
GH-326: New 'dateAdd' EL function to enable specifying dataset ranges based on date deltas
------------------------------------------------------------------------------------------
Key: OOZIE-244
URL: https://issues.apache.org/jira/browse/OOZIE-244
Project: Oozie
Issue Type: Bug
Reporter: Hadoop QA
Currently dataset ranges are specified as frequency ranges, for many developers it is more natural to think in date ranges rather than frequency ranges.
For example for an half-hourly dataset, today, the 48 instances for the the last day are expressed as the following range:
<code>
<start-instance>${coord:current(-47)}</start-instance>
<end-instance>${coord:current(0)}</end-instance>
</code>
With the new 'dateAdd' EL function it would be:
<code>
<start-instance>${coord:dateAdd(coord:nominalTime(), -1, DAY)}</start-instance>
<end-instance>${coord:nominalTime()}</end-instance>
</code>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (OOZIE-244) GH-326: New 'dateAdd' EL function to
enable specifying dataset ranges based on date deltas
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik reopened OOZIE-244:
------------------------------------
> GH-326: New 'dateAdd' EL function to enable specifying dataset ranges based on date deltas
> ------------------------------------------------------------------------------------------
>
> Key: OOZIE-244
> URL: https://issues.apache.org/jira/browse/OOZIE-244
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Currently dataset ranges are specified as frequency ranges, for many developers it is more natural to think in date ranges rather than frequency ranges.
> For example for an half-hourly dataset, today, the 48 instances for the the last day are expressed as the following range:
> <code>
> <start-instance>${coord:current(-47)}</start-instance>
> <end-instance>${coord:current(0)}</end-instance>
> </code>
> With the new 'dateAdd' EL function it would be:
> <code>
> <start-instance>${coord:dateAdd(coord:nominalTime(), -1, DAY)}</start-instance>
> <end-instance>${coord:nominalTime()}</end-instance>
> </code>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OOZIE-244) GH-326: New 'dateAdd' EL function to
enable specifying dataset ranges based on date deltas
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadoop QA resolved OOZIE-244.
-----------------------------
Resolution: Fixed
> GH-326: New 'dateAdd' EL function to enable specifying dataset ranges based on date deltas
> ------------------------------------------------------------------------------------------
>
> Key: OOZIE-244
> URL: https://issues.apache.org/jira/browse/OOZIE-244
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Currently dataset ranges are specified as frequency ranges, for many developers it is more natural to think in date ranges rather than frequency ranges.
> For example for an half-hourly dataset, today, the 48 instances for the the last day are expressed as the following range:
> <code>
> <start-instance>${coord:current(-47)}</start-instance>
> <end-instance>${coord:current(0)}</end-instance>
> </code>
> With the new 'dateAdd' EL function it would be:
> <code>
> <start-instance>${coord:dateAdd(coord:nominalTime(), -1, DAY)}</start-instance>
> <end-instance>${coord:nominalTime()}</end-instance>
> </code>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira