[
https://issues.apache.org/jira/browse/BEAM-5495?focusedWorklogId=358800&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-358800
]
ASF GitHub Bot logged work on BEAM-5495:
----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Dec/19 16:58
Start Date: 12/Dec/19 16:58
Worklog Time Spent: 10m
Work Description: lgajowy commented on issue #10268: [BEAM-5495]
PipelineResources algorithm is not working in most environments
URL: https://github.com/apache/beam/pull/10268#issuecomment-565092515
I think I know what the problem was - the error was due to the fact that
classGraph returns .gradle/wrapper/* jars too. The previous algorithm (based
only on urlClassLoader) couldn't do that. We're unable to stage wrapper's - the
jars are already in use by ./gradlew process. Filtering out the jars helps.
----------------------------------------------------------------
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: 358800)
Time Spent: 12h (was: 11h 50m)
> PipelineResources algorithm is not working in most environments
> ---------------------------------------------------------------
>
> Key: BEAM-5495
> URL: https://issues.apache.org/jira/browse/BEAM-5495
> Project: Beam
> Issue Type: Bug
> Components: runner-flink, runner-spark, sdk-java-core
> Reporter: Romain Manni-Bucau
> Assignee: Lukasz Gajowy
> Priority: Major
> Time Spent: 12h
> Remaining Estimate: 0h
>
> Issue are:
> 1. it assumes the classloader is an URLClassLoader (not always true and java
> >= 9 breaks that as well for the app loader)
> 2. it uses loader.getURLs() which leads to including the JRE itself in the
> staged file
> Looks like this detect resource algorithm can't work and should be replaced
> by a SPI rather than a built-in and not extensible algorithm. Another valid
> alternative is to just drop that "guess" logic and force the user to set
> staged files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
