Hi,

I want to do windowed aggregation with streams library. However, I get the
output from particular operator immediately, independent of window size.
This makes sense for unlimited windows or sometimes for event time windows.
However, for ingestion time or processing time windows, users may want to
exact results (and in exact time) of windowed aggregation operator.
For example, if I have window of 4 minutes with 2 minutes slide, I would
expect to get an output once per 2 minutes. Otherwise I cannot know which
one of the outputted tuples from aggregator operator is the "right" that
contains aggregation result of whole window.
One solution for this, is using queryable state, but pulling states
regularly to get latest answers is not useful for my usecase.

So, is it on your roadmap to integrate purge/trigger mechanism to windowed
aggregates?

Thanks
Davood

Reply via email to