You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Scott McKinney (Jira)" <ji...@apache.org> on 2019/12/03 02:26:00 UTC
[jira] [Updated] (BEAM-8875) Pipeline fails to run remotely
[ https://issues.apache.org/jira/browse/BEAM-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott McKinney updated BEAM-8875:
---------------------------------
Description:
Beam fails to run remote pipeline when the class loader has URLs other than _[file://_|file://_/]._ The environment uses the [Manifold project|[http://manifold.systems/]], which installs a custom URL handler of the form: _manifoldclass://_, which contributes to the URL classpath, however Beam throws an exception when it encounters this URL. Instead Beam should *ignore* or at most warn about URLs it does not recognize.
A similar issue was recently fixed in the Spring framework: [https://github.com/spring-projects/spring-framework/issues/21950]. Beam should follow suit.
See external Manifold issue: [https://github.com/manifold-systems/manifold/issues/143]
was:
Beam fails to run remote pipeline when the class loader has URLs other than _file://_. The environment uses the [Manifold project|[http://manifold.systems/]], which installs a custom URL handler of the form: _manifoldclass://_, which contributes to the URL classpath, however Beam throws an exception when it encounters this URL. Instead Beam should *ignore* or at most warn about URLs it does not recognize.
A similar issue was recently fixed in the Spring framework: [https://github.com/spring-projects/spring-framework/issues/21950]. Beam should follow suit.
See external Manifold issue: [https://github.com/manifold-systems/manifold/issues/143]
> Pipeline fails to run remotely
> ------------------------------
>
> Key: BEAM-8875
> URL: https://issues.apache.org/jira/browse/BEAM-8875
> Project: Beam
> Issue Type: Bug
> Components: beam-model
> Environment: Java 8
> Reporter: Scott McKinney
> Priority: Blocker
>
> Beam fails to run remote pipeline when the class loader has URLs other than _[file://_|file://_/]._ The environment uses the [Manifold project|[http://manifold.systems/]], which installs a custom URL handler of the form: _manifoldclass://_, which contributes to the URL classpath, however Beam throws an exception when it encounters this URL. Instead Beam should *ignore* or at most warn about URLs it does not recognize.
> A similar issue was recently fixed in the Spring framework: [https://github.com/spring-projects/spring-framework/issues/21950]. Beam should follow suit.
> See external Manifold issue: [https://github.com/manifold-systems/manifold/issues/143]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)