Thanks Gabor

It’s indeed true. But in the “old way” I could give my state variables scope access and I could then access the state from my test and assert the state. Much simpler approach. 

I was hoping for a simpler solution than use the state processer api


Med venlig hilsen / Best regards
Lasse Nedergaard


Den 18. jun. 2025 kl. 13.30 skrev Gabor Somogyi <gabor.g.somo...@gmail.com>:


Hi Lasse,

Not sure what kind of code you have but depending on Flink internals as user is discouraged.
Instead one can write state into temp dir and can use State Processor API [1] to read/assert on the content.

BR,
G



On Wed, Jun 18, 2025 at 1:07 PM Lasse Nedergaard <lassenedergaardfl...@gmail.com> wrote:
Hi.

I’m playing around with the new DataStream api and I’m struggling figure out how to access the keyed state from test harness so I can validate correct update, clean up etc.

Can anyone help me with hints for testing the internal state it would be much appreciated.

Best regards
Lasse Nedergaard

Reply via email to