fix beam-runners-flink and zeppelin-scio scala version to 2.10

[avnerl]

What is this PR for?

build is failing when trying to use scala-2.11 profile

• beam-runners-flink 2.0.0 was never built with anything other than scala 2.10, therefore parametrizing its scala version breaks the build.
• scio is hard coded with scala 2.10, therefore parametrizing its scala version breaks the build.

What type of PR is it?

[Hot Fix]

Todos

• - merge or handle zeppelin-scio and beam-runner-flink scala versions

What is the Jira issue?

• N/A

How should this be tested?

• Pass CI
• manual build:

mvn clean package -Pbuild-distr -DskipTests -Pspark-2.4 -Phadoop-2.7 -Pscala-2.11

Screenshots (if appropriate)

Questions:

• no licenses files need update
• no breaking changes for older versions
• Does this needs documentation? not sure

[felixcheung]

hm, yes, but then building -Pscala-2.11 will provide scala-2.10 output? that's kinda weird.

[avnerl]

you are right. it didn't make sense. the reason i did this is because i wanted the build to pass. i remove the beam interpreter afterwards as i dont need it.
last 2 commits revert back to parameterized scala version in beam, and introduced a new beam build profile that bump beam version to 2.3.0 when when building with -Pscala-2.11.

[avnerl]

do you think it's a good idea to tamper with beam version in dev/change_scala_version.sh too?
build will not pass if you do not use the -Pscala-2.11 profile explicitly

[felixcheung]

what about we don't build beam and scio if scala-2.11?

[felixcheung]

also we could upgrade beam interpreter to "require" beam 2.3 also (so it does build with scala-2.11)

[avnerl]

also we could upgrade beam interpreter to "require" beam 2.3 also (so it does build with scala-2.11)

that's what i did in: ffca03c

do you have a better approach?

[felixcheung]

that's what i did in: ffca03c

ah, that would make different versions of beam with scala-2.10 or scala-2.11.

is there a scio version that works with scala-2.11? what if we upgrade the supported version of beam and scio in all profile?

[avnerl]

that's what i did in: ffca03c

ah, that would make different versions of beam with scala-2.10 or scala-2.11.

is there a scio version that works with scala-2.11? what if we upgrade the supported version of beam and scio in all profile?

we don't have much choice here. beam was never crossed built with scala. starting version 2.3.0 it is built with 2.11 only (prior versions with 2.10).
so changing scala version implies changing beam version as well.
scio 0.2.4 is cross built with both 2.10 and 2.11, so it is already being taken care of.

[avnerl]

https://mvnrepository.com/artifact/org.apache.beam/beam-runners-flink

[felixcheung]

in that case, can we make it build beam only when it has support for it.
ie. build scala 2.10 - beam 2.0.0
build scala 2.11 - beam not included (but not failing)

[avnerl]

closing this for lack of time. i'll use this for my own testing:
mvn clean package -Pbuild-distr -DskipTests -Pspark-2.4 -Phadoop-2.7 -Pscala-2.11 -p !beam