Hi,

Since currently State Processor doesn’t support window states, what’s the 
recommended way to debug window states?

The background is that I have a SQL job whose states, mainly window aggregation 
operator states, keep increasing steadily.

The things I’ve checked:
- Outputs are as expected.
- Keys amount are capped.
- Watermarks are good, no lags.
- No back pressure.

If I can directly read the states to find out what’s accountable for the state 
size growth, that would be very intuitional and time-saving.

Best,
Paul Lam

Reply via email to