You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2017/04/27 15:16:04 UTC

[jira] [Updated] (TEZ-3702) Tez shuffle jar includes service loader entry for ClientProtocolProvider but not the corresponding class

     [ https://issues.apache.org/jira/browse/TEZ-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe updated TEZ-3702:
----------------------------
    Attachment: TEZ-3702.001.patch

It doesn't look like the shuffle handler really needs the tez-mapreduce dependency at all.  The shuffle handler was pulling in MRConfig.SHUFFLE_SSL_ENABLED_KEY, but that's a mapreduce property instead of a tez one.  Arguably it should be a property specific to the tez shuffle handler rather than the mapreduce shuffle handler.

The only other reference was in a unit test that appeared to be unnecessary.  Removing these allowed the removal of the dependency, and that fixes the bogus service loader entry being pulled in during shading.

> Tez shuffle jar includes service loader entry for ClientProtocolProvider but not the corresponding class
> --------------------------------------------------------------------------------------------------------
>
>                 Key: TEZ-3702
>                 URL: https://issues.apache.org/jira/browse/TEZ-3702
>             Project: Apache Tez
>          Issue Type: Sub-task
>    Affects Versions: TEZ-3334
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: TEZ-3702.001.patch
>
>
> The tez-aux-shuffle jar is shading the tez-mapreduce dependency but that causes the service loader entry for org.apache.hadoop.mapreduce.protocol.ClientProtocolProvider to be included without including the referenced org.apache.tez.mapreduce.client.YarnTezClientProtocolProvider class.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)