Doh! Sorry about that! :) Thanks again!
On Thu, Mar 28, 2019 at 12:49 PM Dawid Wysakowicz <dwysakow...@apache.org> wrote: > I did ;) but here is the link one more time: > https://issues.apache.org/jira/browse/FLINK-11017?jql=project%20%3D%20FLINK%20AND%20text%20~%20Month > > On Thu, 28 Mar 2019, 20:48 Vinod Mehra, <vme...@lyft.com> wrote: > >> Thanks Dawid! Can you please point me to a jira which tracked the fix? >> >> Thanks! >> Vinod >> >> On Thu, Mar 28, 2019 at 12:46 PM Dawid Wysakowicz <dwysakow...@apache.org> >> wrote: >> >>> It should be fixed since version 1.6.3. >>> Best, >>> Dawid >>> >>> >>> [1] >>> https://issues.apache.org/jira/browse/FLINK-11017?jql=project%20%3D%20FLINK%20AND%20text%20~%20Month >>> >>> >>> On Thu, 28 Mar 2019, 19:32 Vinod Mehra, <vme...@lyft.com> wrote: >>> >>>> Hi All! >>>> >>>> We are using: org.apache.flink:flink-table_2.11:jar:1.4.2:compile >>>> >>>> SELECT >>>> COALESCE(user_id, -1) AS user_id, >>>> count(id) AS count_per_window, >>>> sum(amount) AS charge_amount_per_window, >>>> TUMBLE_START(rowtime, INTERVAL '2' YEAR) AS twindow_start, >>>> TUMBLE_END(rowtime, INTERVAL '2' YEAR) AS twindow_end >>>> FROM >>>> event_charge_processed >>>> WHERE capture=true >>>> AND COALESCE(user_id, -1) <> -1 >>>> GROUP BY >>>> TUMBLE(rowtime, INTERVAL '2' YEAR), >>>> COALESCE(user_id, -1) >>>> >>>> For '1' MONTH intervals it results in 1ms windows, 2 MONTH=2ms, 3 >>>> MONTH=3ms …. 1 YEAR=12ms, 2 YEAR=24ms! Which results in incorrect >>>> aggregations. >>>> >>>> I found that org.apache.calcite.sql.SqlLiteral#getValueAs() treats >>>> MONTH/YEAR differently than DAY/HOUR etc. Perhaps the bug is somewhere >>>> there (?). >>>> >>>> Is this a known issue? Has it been fixed in later versions? >>>> >>>> Thanks, >>>> Vinod >>>> >>>>
