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
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.
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:/
Hi,
I found that if I convert a Datastream into Table and back into Datastream,
watermark of the stream will be lost. As shown in the program below, the
TestOperator before the conversion will have its processWatermark() method
triggered and watermark value printed, but the one after the conversio
