[
https://issues.apache.org/jira/browse/BEAM-2530?focusedWorklogId=213678&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-213678
]
ASF GitHub Bot logged work on BEAM-2530:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Mar/19 10:29
Start Date: 15/Mar/19 10:29
Worklog Time Spent: 10m
Work Description: adude3141 commented on issue #8031: [BEAM-2530]
Automatically retrieving JDK 11 containers in Dataflow
URL: https://github.com/apache/beam/pull/8031#issuecomment-473234251
Unfortunately I do not fully understand the changes here.
I assume we are talking about some container, a beam pipeline is run with?
I.e. the container is running beam code and user code.
I further assume, the customer is allowed to provide her code compiled with
java8. So will likely not test on java11 herself, but that containers java
version would be kind of transparent to her.
Now given a business critical pipeline depending on some third-party library
which can not easily be replaced nor upgraded. Which in turn depends for
instance on some byte code enhancement lib or does such simple things as
`(URLClassLoader) getClass().getClassLoader()`
which, iirc does not work anymore on java11 (or some such I do not remember).
Wouldn't that mean, that this customer is suddenly locked out of the
service? Always assuming that for whatever reason it is not feasible to upgrade
those deps.
Although, in general it is true that code should just run. But I guess we
can not guarantee this.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 213678)
Time Spent: 4.5h (was: 4h 20m)
> Make Beam compatible with next Java LTS version (Java 11)
> ---------------------------------------------------------
>
> Key: BEAM-2530
> URL: https://issues.apache.org/jira/browse/BEAM-2530
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Affects Versions: Not applicable
> Reporter: Ismaël Mejía
> Priority: Minor
> Labels: java9
> Fix For: Not applicable
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> The goal of this task is to validate that the Java SDK and the Java Direct
> Runner (and its tests) work as intended on the next Java LTS version (Java 11
> /18.9). For this we will base the compilation on the java.base profile and
> include other core Java modules when needed.
> *Notes:*
> - Ideally validation of the IOs/extensions will be included but if serious
> issues are found they will be tracked independently.
> - The goal of using the Java Platform module system is out of the scope of
> this work.
> - Support for other runners will be a tracked as a separate effort because
> other runners depend strongly in the support of the native runner ecosystems.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
