Re: Table DataStream Conversion Lost Watermark

2021-12-06 Thread Yunfeng Zhou
Hi Timo, Thanks for this information. Since it is confirmed that toDataStream is functioning correctly and that I can avoid this problem by not using fromValues in my implementation, I think I have got enough information for my current work and don't need to rediscuss fromDatastream's behavior. B

Re: Table DataStream Conversion Lost Watermark

2021-12-06 Thread Timo Walther
Hi Yunfeng, it seems this is a deeper issue with the fromValues implementation. Under the hood, it still uses the deprecated InputFormat stack. And as far as I can see, there we don't emit a final MAX_WATERMARK. I will definitely forward this. But toDataStream forwards watermarks correctly.

Re: Table DataStream Conversion Lost Watermark

2021-11-05 Thread Timo Walther
Hi Yunfeng, by default the fromDataStream does not propagate watermarks into Table API. Because Table API needs a time attribute in the schema that corresponds to the watermarking. A time attribute will also put back into the stream record during toDataStream. Please take a look at: https:/