[
https://issues.apache.org/jira/browse/BEAM-13468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480306#comment-17480306
]
Clément Guillaume commented on BEAM-13468:
------------------------------------------
I made some progress but this is not very good.
* I'm not happy with how I fallback on java11 for the static variable
JAVA_SDK_HARNESS_ENVIRONMENT
* I'm not happy with how I fallback on the current runtime version in too many
places
* I'm not sure I can access the pipeline option in {{SdkComponents.create}},
see stacktrace
!Screenshot from 2022-01-21 16-10-20.png!
the code is visible at
https://github.com/guillaumecle/beam/commit/628075d0a64af0489712e79be67dbd663b6b71ed
> 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
> Priority: P2
> Attachments: 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)
