You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2020/04/28 14:46:00 UTC

[jira] [Comment Edited] (TEZ-4157) Remove unused direct netty dependency

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

László Bodor edited comment on TEZ-4157 at 4/28/20, 2:45 PM:
-------------------------------------------------------------

thanks for taking a look [~ashutoshc], [~jeagles]
[~jeagles]: yeah, it seems like I missed that as it compiled successfully because of transitive dependencies...
what do you think about netty 4 upgrade and remove netty3 from tez? hadoop has both of them, so:

1. we can upgrade to netty 4.0.52.Final to stay inline with hadoop (however this will cause further alerts as 4.0.52 also affected by CVS-s) -> I can start with this option right now (actually, ShuffleHandler uses it heavily)
2. upgrade to latest netty



was (Author: abstractdog):
thanks for taking a look [~ashutoshc], [~jeagles]
[~jeagles]: yeah, it seems like I missed that as it compiled successfully because of transitive dependencies...
what do you think about netty 4 upgrade and remove netty3 from tez? hadoop has both of them, so:

1. we can upgrade to netty 4.0.52.Final to stay inline with hadoop (however this will cause further alerts as 4.0.52 also affected by CVS-s) -> I can start with this option right now
2. upgrade to latest netty


> Remove unused direct netty dependency
> -------------------------------------
>
>                 Key: TEZ-4157
>                 URL: https://issues.apache.org/jira/browse/TEZ-4157
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Major
>         Attachments: TEZ-4157.01.patch
>
>
> In the dependency tree, there are 2 occurrences of compile scope direct netty dependencies, however, they're not used at all. I compiled locally successfully without them.
> E.g. when investigating blackduck alerts (complaining about netty deps for current 3.10.5.Final), it would be cleaner to start from a dependency tree where Tez doesn't depend on netty directly in order to eliminate its responsibility (and move the focus to underlying hadoop for instance).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)