[jira] [Commented] (BEAM-8875) Pipeline fails to run remotely

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169344#comment-17169344 ] 

Beam JIRA Bot commented on BEAM-8875:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Pipeline fails to run remotely
> ------------------------------
>
>                 Key: BEAM-8875
>                 URL: https://issues.apache.org/jira/browse/BEAM-8875
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core, runner-dataflow
>         Environment: Java 8
>            Reporter: Scott McKinney
>            Priority: P2
>              Labels: stale-P2
>
> 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)