[
https://issues.apache.org/jira/browse/BEAM-13468?focusedWorklogId=752552&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-752552
]
ASF GitHub Bot logged work on BEAM-13468:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Apr/22 23:28
Start Date: 04/Apr/22 23:28
Worklog Time Spent: 10m
Work Description: guillaumecle opened a new pull request, #17274:
URL: https://github.com/apache/beam/pull/17274
It possible to run beam on a non-lts jvm: either using the direct runner or
uploading java code compiled in a supported version to the remote runner.
This pull request, stop throwing Exception when the current jvm is a
non-lts, instead it's falling back to java 11 for the runner version.
I was able to successfully run a java 11 dataflow job from a java 15 jvm.
I think this will also fix BEAM-12408 (Direct Runner cannot be run on non
Java LTS versions)
R: @kileys
Issue Time Tracking
-------------------
Worklog Id: (was: 752552)
Remaining Estimate: 0h
Time Spent: 10m
> Dataflow runner - be more lenient with agent java version
> ---------------------------------------------------------
>
> Key: BEAM-13468
> URL: https://issues.apache.org/jira/browse/BEAM-13468
> Project: Beam
> Issue Type: New Feature
> Components: runner-dataflow
> Reporter: Clément Guillaume
> Assignee: Clément Guillaume
> Priority: P2
> Attachments: BEAM-13468-version-as-option.patch, Screenshot from
> 2022-01-21 16-10-20.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> DataflowRunner currently uses {{Environments.getJavaVersion}} to detect java
> version and build the Dataflow user agent string.
> {{Environments.getJavaVersion}} only accept a small subset of java version
> (8, 11 and 17)
> It would be nice the user agent string to accept more exotic java versions to
> allow running the agent on more exotic jvm (still keeping the beam model
> itself in java 11).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
