[
https://issues.apache.org/jira/browse/BEAM-13468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516145#comment-17516145
]
Clément Guillaume commented on BEAM-13468:
------------------------------------------
I'll take another stab at it with another approach: if the jvm is not one of
recognized ones, fallback on java 11 (I think we can still try later to
implement java version as a job option)
> 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
>
>
> 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)
