@Robert Why would he have to recompile the jobs? Shouldn't he be fine
soo long as he isn't using any API for which we broke binary-compatibility?
On 09/04/2020 09:55, Robert Metzger wrote:
Hey Stephen,
1. You should be able to migrate from 1.8 to 1.10:
https://ci.apache.org/projects/flink/flink-docs-release-1.10/ops/upgrading.html#compatibility-table
2. Yes, you need to recompile (but ideally you don't need to change
anything).
On Mon, Apr 6, 2020 at 10:19 AM Stephen Connolly
<stephen.alan.conno...@gmail.com
<mailto:stephen.alan.conno...@gmail.com>> wrote:
Quick questions on upgrading Flink.
All our jobs are compiled against Flink 1.8.x
We are planning to upgrade to 1.10.x
1. Is the recommended path to upgrade one minor at a time, i.e.
1.8.x -> 1.9.x and then 1.9.x -> 1.10.x as a second step or is the
big jump supported, i.e. 1.8.x -> 1.10.x in one change
2. Do we need to recompile the jobs against the newer Flink
version before upgrading? Coordinating multiple teams can be
tricky, so - short of spinning up a second flink cluster - our
continuous deployment infrastructure will try to deploy the
topologies compiled against 1.8.x for an hour or two after we have
upgraded the cluster
