read records from the 10 partitions, and it may well that
>>>> the records will arrive the window process operator out of order.
>>>> Is it possible that the records exceed the watermark, but there're still
>>>> some records will arrive?
>>>>
&g
t; If that's the case, every time, the records used to calculate result may
> well different and then result in non-determinism result.
>
> Best regards,
> Yuxia
>
> - 原始邮件 -
> 发件人: "Theodor Wübker"
> 收件人: "User"
> 发送时间: 星期日, 2023年 2 月 12日
eed the watermark, but there're still
>>> some records will arrive?
>>>
>>> If that's the case, every time, the records used to calculate result may
>>> well different and then result in non-determinism result.
>>>
>>> Best regards,
>
different and then result in non-determinism result.
>>
>> Best regards,
>> Yuxia
>>
>> - 原始邮件 -
>> 发件人: "Theodor Wübker" > <mailto:theo.wueb...@inside-m2m.de>>
>> 收件人: "User" mailto:user@flink.apache.org>>
>>
"User"
发送时间: 星期日, 2023年 2 月 12日 下午 4:25:45
主题: Non-Determinism in Table-API with Kafka and Event Time
Hey everyone,
I experience non-determinism in my Table API Program at the moment and (as a
relatively unexperienced Flink and Kafka user) I can’t really explain to myself
why it
Hey everyone,
I experience non-determinism in my Table API Program at the moment and (as a
relatively unexperienced Flink and Kafka user) I can’t really explain to myself
why it happens. So, I have a topic with 10 Partitions and a bit of Data on it.
Now I run a simple SELECT * query on this, t
