[
https://issues.apache.org/jira/browse/BEAM-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738451#comment-16738451
]
Chamikara Jayalath commented on BEAM-3519:
------------------------------------------
We have upgraded gRPC and netty dependencies used by GCP IO. I think problem
previously was exacerbated due to GCP IO using a very old version of gRPC and
netty. Now that we have upgraded hopefully the issue is not as severe as it
used to be (i.e. as long as other modules also use new/compatible gRPC/netty
versions things should be fine). I agree that to fully isolate modules from
each other we have to shade away gRPC/netty.
> 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: Chamikara Jayalath
> 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)
