Your are right that it's not thread-safety.
I think we can use Collections.synchronizedList() to get a thread-safety
list[1].
And remove the synchronized keyword from the invoke interface.
I have created a ticket to track this[2], please feel free to fix it by
make a pull request.
[1]
https://doc
Hi all,
I think the code example in following section has a thread safety issue:
https://ci.apache.org/projects/flink/flink-docs-release-1.9/dev/stream/testing.html#junit-rule-miniclusterwithclientresource
The class CollectSink is not thread safe as only the write to the values
collection are sync