Re: RE:[DISCUSS] FLIP-11: Table API Stream Aggregations

2016-10-14 Thread Timo Walther
ream * FROM Order WHERE userID='A'") So in my opinion, the grammar which is marked red should be compatible with calcite's StreamSQL grammar. By the way, thanks very much for telling me the modified content in Flink StreamSQL. I will look the new proposal . Thanks! 发件人: Sean

re: RE:[DISCUSS] FLIP-11: Table API Stream Aggregations

2016-10-13 Thread Zhangrucong
t;> .map(f=>(f, 1L, 1L)) >> val sql = tblEnv.sql("SELECT Stream * FROM Order WHERE userID='A'") >> >> So in my opinion, the grammar which is marked red should be >> compatible with calcite's StreamSQL grammar. >> >> By the way

Re: RE:[DISCUSS] FLIP-11: Table API Stream Aggregations

2016-10-13 Thread Sean Wang
Hi zhangrucong, I am not sure what you mean by "table API'S StreamSQL", I guess you mean "stream TableAPI"? TableAPI should be compatible with calcite SQL. (By compatible, My understanding is that both TableAPI and SQL will be translated to the same logical plan - the same set of REL and REX). BTW

Re: RE:[DISCUSS] FLIP-11: Table API Stream Aggregations

2016-10-12 Thread Zhangrucong
Hi shaoxuan: Does the table API'S StreamSQL grammar is compatible with calcite's StreamSQL grammar? 1、In calcite, the tumble window is realized by using function tumble or hop. And the function must be used with group by, like this: SELECT TUMBLE_END(rowtime, INTERVAL '30' MINUTE, TIME '0: