Hi Gabriele, use (or extend) the window operator provided by Flink is a
better idea. A window operator in Flink manages two types of state:
- Window state: accumlate data for windows, and provide data to window
function when a window comes to its end time.
- Timer state: store the end tim
Hi Gabriele,
The keyed state APIs (ValueState、ListState、etc) are supported by all
types of state backend (hashmap、rocksdb、etc.). And the built-in window
operators are implemented with these state APIs internally. So you can use
these built-in operators/functions with the RocksDB state backend
Hi Gabriele,
Quick answer: You can use the built-in window operators which have been
integrated with state backends including RocksDB.
Thanks,
Zakelly
On Tue, Mar 5, 2024 at 10:33 AM Zhanghao Chen
wrote:
> Hi Gabriele,
>
> I'd recommend extending the existing window function whenever possible
Hi Gabriele,
I'd recommend extending the existing window function whenever possible, as
Flink will automatically cover state management for you and no need to be
concerned with state backend details. Incremental aggregation for reduce state
size is also out of the box if your usage can be satis
