Regarding to **L.window_start = R.window_start AND L.window_end =
R.window_end**:
In general, the current table function windowing model is to append window
metadata to table directly, thus window metadata becomes a part of table
(or call it data). So as a part of table, these two columns should b
Is there any possibility that 1.26.0 can be released in the following weeks,
e.g. within the October ?
Apache Flink would release next major version in the end of October, if we can
use the latest Calcite code, that would be awesome ~
Best,
Danny Chan
Yes, the red part is **L.window_start = R.window_start AND L.window_end =
R.window_end**
> Is this a limitation for "triggered by the watermark of the stream”?
No, because in most of the cases, there is no need to output the
intermediate/partial join records then send retractions.
So, how do
Hi Danny,
seems like the "Red" syntax is missing? I am guessing you were talking
about "L.window_start = R.window_start AND L.window_end = R.window_end"?
Can you use ** to indicate the red part.
Two additional questions:
> The Join action is triggered by the watermark of the stream
So sounds lik
Sorry, but what part is red. Your markup appears to have been stripped.
James
On Tue, Sep 22, 2020 at 9:05 PM Danny Chan wrote:
> Hi, fellows, long time no see on the mailing ~
>
> Here I want to have a discussion on the join syntax of our recently
> introduced window table function ~
>
> For
Hi, fellows, long time no see on the mailing ~
Here I want to have a discussion on the join syntax of our recently introduced
window table function ~
For example, we can define a tumbling window function of 5 minutes size as:
Tumble(table T, descriptor(T.ts), INTERVAL ‘5’ MINUTE)
The we can se
Is there a better way?
I'm am idealist with regard to streaming SQL semantics, and I'm going
to make the 'slippery slope' argument that if we add a TIMEOUT
parameter to MATCH_RECOGNIZE, won't we also need to add it to GROUP BY
and JOIN? (Because those are also "blocking" operators.)
Maybe JOIN an
Wang Yanlin created CALCITE-4273:
Summary: Support get expression lineage for Calc
Key: CALCITE-4273
URL: https://issues.apache.org/jira/browse/CALCITE-4273
Project: Calcite
Issue Type: Impro
