Re: FW: [DISCUSS] Table API / SQL indicators for event and processing time

2017-03-27 Thread Fabian Hueske
:twal...@apache.org] > Sent: Monday, March 20, 2017 2:05 PM > To: dev@flink.apache.org > Subject: Re: FW: [DISCUSS] Table API / SQL indicators for event and > processing time > > Yes, you are right. In the current design the user cannot assign > timestamp and watermarks in a table pr

RE: FW: [DISCUSS] Table API / SQL indicators for event and processing time

2017-03-20 Thread Radu Tudoran
To: dev@flink.apache.org Subject: Re: FW: [DISCUSS] Table API / SQL indicators for event and processing time Yes, you are right. In the current design the user cannot assign timestamp and watermarks in a table program. Operators (such as windows) might adapt the metatimestamp, if this is the

Re: FW: [DISCUSS] Table API / SQL indicators for event and processing time

2017-03-20 Thread Timo Walther
Yes, you are right. In the current design the user cannot assign timestamp and watermarks in a table program. Operators (such as windows) might adapt the metatimestamp, if this is the case this adaption might need to be expressed in the query itself too. E.g. for a tumbling windows we could li

FW: [DISCUSS] Table API / SQL indicators for event and processing time

2017-03-20 Thread Radu Tudoran
Hi, As suggested by Timo - I am forwarding this to the mailing list. Sorry for not having the conversation directly here - I initially thought it might not be of interest... @Timo - thanks for the clarification. I get the main point now which is that the rowtime is encoded within the metadata