Presumably you switched between branches / points in Flinks development,
and either
a) at the commit you are at the flink-rpc module didn't exist yet (but
IntelliJ still displays it because the directory is still present) or
b) IntelliJ hasn't caught up with new modules in which case reloading
t
I see, that's how it works. Thanks!
Slightly related, which made it a little hard to navigate the code. I'm
using IntelliJ and for some reason navigating the code in flink-rpc doesn't
work. It's not listed as a module. In the Project-view it is there, but
with a different icon than e.g flink-runti
There is some internal magic going on. Have a look at the interface the
handlers work against, you will see that the timeout parameter is
annotated with @RpcTimeout. The AkkaInvocationHandler extracts the
timeout based on this annotation and uses it internally.
On 24/08/2021 12:05, Juha Myntti
Hey,
I was looking at the web.timeout configuration option described as "Timeout
for asynchronous operations by the web monitor in milliseconds". I'm
interested in where and how it's used internally.
I've understood it's the timeout when the Web UI calls something using Rpc
(Akka). Correct? Unfor
