You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2018/03/28 08:09:00 UTC

[jira] [Commented] (BEAM-1492) Avoid potential issue in ASM 5.0

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

Ismaël Mejía commented on BEAM-1492:
------------------------------------

After the move to spark 2 the spark runner uses a a shaded version of kryo that shades asm 5.0.1. If the issue happens in the spark runner it should be probably fixed upstream. No news so far on this issue so I am marking it as invalid hoping it does not bite us in the future.

> Avoid potential issue in ASM 5.0
> --------------------------------
>
>                 Key: BEAM-1492
>                 URL: https://issues.apache.org/jira/browse/BEAM-1492
>             Project: Beam
>          Issue Type: Task
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Assignee: Amit Sela
>            Priority: Major
>             Fix For: 2.4.0
>
>
> There is a suspected bug in asm 5.0 that is considered the likely root cause of a [bug sbt-assembly|https://github.com/sbt/sbt-assembly/issues/205#issuecomment-279964607] that carried over to [GEARPUMP-236]. I have not found a direct reference to what the issue is, precisely, but the dependency effect of this is extremely small and these are libraries that are useful to keep current. And if/when Gearpump runner lands on master this will avoid any diamond dep issues.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)