You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/18 17:07:16 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=17179819#comment-17179819 ] 

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

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.


> 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
>            Priority: P2
>              Labels: stale-P2
>          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
(v8.3.4#803005)