On Sun, Nov 30, 2014 at 6:54 AM, Idris Ali <[email protected]> wrote:
>
> If the intention is to read hourly data for a month, then the simplest way
> is to specify like this.
>
> <data-in name="input" dataset="logs">
> <start-instance>${coord:current( -(coord:daysInMonth(0) -
> 1)*24 )}</start-instance>
> <end-instance>${coord:current(0)}</end-instance>
> </data-in>
>
> This takes care of any month, however special handling is required for
> daylight saving timezone, for details refer the coordinator functional spec
> here.
Yes, that is indeed the intention and this was my first thought. However,
it is the special handling for daylight saving time that I am specifically
looking to avoid. I don't see anything in the coordinator functional spec
that will help with this. The coord:hoursInDay() function is great, but
what is needed in this case is a coord:hoursInMonth() function.
That said, I thought the approach of using the coord:offset() function
would be a good way of doing this, but I've hit what appears to be a bug.
Can anyone confirm that this is indeed a bug? Does anyone know of a good
workaround, either with coord:daysInMonth()/hoursInDay() or some other way?
Is it possible to extend the EL language locally to support an
hoursInMonth() method?
Any help would be appreciated. Thanks,
- J.
