I think the issue is independent of releasing since it is a CI thing. And I
think Yi is actually pointing out that it will be a user thing (since users
will want to use newer JDK also)
But still I agree that as the project matures the pro/con of making modules
more independent changes. So if that
Hi,
issues like this arise from the fact that we have tight coupling between
various parts of our ecosystem - the model, the core and runners. We
should decouple this and enable runners to have their own release
cycles, because anything other will not scale in the long run. We cannot
have mor
Yes currently we use --target 8 for all Beam modules at compiling. The
issues above are for incompatibility at execution time, and indeed not
fixed by these flags.
Currently we run Samza and Spark 3.4.0 tests on JDK 1.8 as a workaround.
Using JDK11 with cross-compiling did not help as the compatib
Are we using --target 8 in the Ci/CD and/or --source 8 for some modules?
Are the problems independent of what those flags control?
Just curious - I am not advocating for anything.
Kenn
On Mon, Nov 25, 2024 at 1:38 PM Yi Hu via dev wrote:
> Hi Beam community,
>
> As Beam repo CI/CD has moved to
Hi Beam community,
As Beam repo CI/CD has moved to Java 11 [1], I would like to bring up
attention to two outstanding open Issues that could affect Spark and Samza
runner users [2, 3]
For Spark Runner issue, currently Spark runner does not support Spark
3.4.0+ with Java11. This is due to Spark 3.
