Thanks for you response!
Yes, I think to 99.9% there shouldn't be a "late event" and I would also
implement a logic in the ProcessFunction, which checks for a specific order
of the events per transaction id.
Using the clear() function for the state should free the ressources and
using that many
Your approach with ProcessFunction should work in general.
Can you guarantee that no event can arrive for a transaction for which
an aggregated event
was already emitted?
On 26.11.2017 18:22, Lothium wrote:
Hi,
I have a question to a specific use case and hope that you can help me with
that.
