Thanks for bring up this discussion Kenn!
Definitely +1 for the proposal.
I have left some questions in the documentation :)
Best,
Jincheng
Rui Wang 于2019年12月11日周三 上午5:23写道：
> Until now as I am not seeing more people are commenting on this proposal,
> can we consider this proposal is already
We hope it does enter the SQL standard. It is one reason for coming
together to write this paper.
OVER clause is mentioned often.
- TUMBLE can actually just be a function so you don't need OVER or any of
the fancy stuff we propose; it is just done to make them all look similar
- HOP still
+1 to remove those magic words in Calcite streaming SQL, just because
they're not SQL standard. The idea to replace HOP/TUMBLE with
table-view-functions makes it concise, my only question is, is it(or will
it be) part of SQL standard? --I'm a big fan to align with standards :lol
Ps, although the
Thanks Kenn,
great paper and left some newbie questions on the proposal.
Manu
On Fri, Jul 19, 2019 at 1:51 AM Kenneth Knowles wrote:
> Hi all,
>
> I recently had the great privilege to work with others from Beam plus
> Calcite and Flink SQL contributors to build a new and minimal proposal for
Hi all,
I recently had the great privilege to work with others from Beam plus
Calcite and Flink SQL contributors to build a new and minimal proposal for
adding streaming extensions to standard SQL: event time, watermarks,
windowing, triggers, stream materialization.
We hope this will influence
