This in general is not a good idea, as the state you query using queryable state within a job does not provide any consistency guarantees at all.
Would it be possible to have some trigger that emits state of the windows, and join the states downstream? In general, that is a better approach for what you seem to be trying to achieve. Otherwise, when it comes to "querying state across operators", that's a hint where the Stateful Functions [1] model could maybe be a better fit to your use case here. Specifically, using Stateful Functions, you would model "querying state" as a request to the target function, with the target function sending its state back as a response. Cheers, Gordon [1] https://flink.apache.org/stateful-functions.html -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
