Hi Ashwin. Thanks for looking into this. Your description of the behaviour and the options matches my understanding, but from my perspective this is a defect: I don't think there's a reasonable interpretation of "period to date" (which is the documented capability) as actually meaning "a full period from beginning to end where the period is the last one for which there is data".

Regarding the CURRENT_DATE() workaround, metrics materialized views can be refreshed as frequently as every hour. I understand that materialization doesn't make sense when there is a genuine dependency on a value that is unknown when the materialized data is calculated, but that is not the case in this example, as we are using "current" time at a granularity three orders of magnitude more coarse than this.

I will use the workaround for now, but is there a process for getting this raised with product / engineering?

Thanks,

Jamie