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

Posted to issues@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2019/01/09 09:09:00 UTC

[jira] [Commented] (BEAM-3519) GCP IO exposes netty on its API surface, causing conflicts with runners

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

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

I have somehow missed the last message [~chamikara]. This is still the case at least until GCP IO gets migrated to use the vendored dependencies.
I am going to reassign this to you so you can see if [~kenn] or someone else at google can work on this.

> GCP IO exposes netty on its API surface, causing conflicts with runners
> -----------------------------------------------------------------------
>
>                 Key: BEAM-3519
>                 URL: https://issues.apache.org/jira/browse/BEAM-3519
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-gcp
>            Reporter: Ismaël Mejía
>            Assignee: Ismaël Mejía
>            Priority: Critical
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
>
> Google Cloud Platform IOs module leaks netty this causes conflicts in particular with execution systems that use conflicting versions of such modules. 
>  For the case there is a dependency conflict with the Spark Runner version of netty, see: BEAM-3492



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