The classic connection pool pattern, where expensive connections are
created relatively few times and used by lots of transient short-lived
tasks, each of which borrows a connection from the pool and returns it when
done, would still be usable here, but as Péter points out, you can't rely
on a sing
Hi Jacob,
Flink jobs, tasks typically run on multiple nodes/servers. This means that
it is not possible to have a connection shared on job level.
You can read about the architecture in more detail in the docs. [1]
I hope this helps,
Péter
[1] -
https://nightlies.apache.org/flink/flink-docs-rele
