Hi all!
I think that in order to get a better hold on how we what to build the
Table API, we need to *decide what the role of the Table API should be*. We
touched on that a few times, but I think we still have different ideas
about that.
To get there, let me take back a step and look at the
Thanks for your quick reply, Fabian.
I have a few minor comments:
- Agree that we should consider GroupBy without window after the new SQL
proposal is settled down.
- For Java API, we can keep window() call, and put window alias into
Groupby clause. This can be also applied to rowwindow case.
Hi Zhangrucong,
yes, we want to use Calcite's SQL parser including its window syntax, i.e.,
- the standard SQL OVER windows (in streaming with a few restriction such
as no different partitionings or orders)
- the GroupBy window functions (TUMBLE, HOP, SESSION).
The GroupBy window function are
Hi everybody,
happy to see a good discussion here :-)
I'll reply to Shaoxuan's mail first and comment on Zhangrucong question in
a separate mail.
Shaoxuan, thanks for the suggestions! I think we all agree that for SQL we
should definitely follow the standard (batch) SQL syntax.
In my opinion,
