[
https://issues.apache.org/jira/browse/BEAM-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kedin updated BEAM-3610:
------------------------------
Description:
Current HOP implementation has parameters in wrong order, according to Calcite
doc. Sliding window size and frequency are swapped
According to [Calcite
docs|https://calcite.apache.org/docs/reference.html#grouped-window-functions]
the syntax is:
{code:SQL}
HOP(timestamp_field, frequency_interval, window_size)
{code}
We have
{code:SQL}
HOP(timestamp_field, window_size, frequency_interval)
{code}
was:Current HOP implementation has parameters in wrong order, according to
Calcite doc. Sliding window size and frequency are swapped
> [SQL] Fix HOP definition
> ------------------------
>
> Key: BEAM-3610
> URL: https://issues.apache.org/jira/browse/BEAM-3610
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql
> Reporter: Anton Kedin
> Priority: Major
>
> Current HOP implementation has parameters in wrong order, according to
> Calcite doc. Sliding window size and frequency are swapped
>
> According to [Calcite
> docs|https://calcite.apache.org/docs/reference.html#grouped-window-functions]
> the syntax is:
> {code:SQL}
> HOP(timestamp_field, frequency_interval, window_size)
> {code}
> We have
> {code:SQL}
> HOP(timestamp_field, window_size, frequency_interval)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
