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

Vinayakumar B commented on HDDS-3604:
-------------------------------------

{quote}Can you please explain this? Based on my understanding Hadoop started to 
shade protobuf AND bumped the protobuf version to a 3.x. Why do we need to use 
2.5 after an upgrade?
{quote}
This is to avoid downstream's classpath/compile breakage due to Protobuf 3.x 
jar's incompatibility with earlier version generated Java files. So hadoop's 
internal usage of protobuf was upgraded, shaded and brought back the old 
version as just for dependency.

But now,to support Hadoop rpc with earlier version of Protobuf, this Jira was 
required.

 
{quote}Is it possible to use Hadoop RPC with any 3.x version of protobuf? Or 
only with the shaded one?
{quote}
Unfortunately, Hadoop RPC with shaded protobuf 3.x supports only shaded 
protobuf, unless some solution is available for that as well.

> Support for Hadoop-3.3
> ----------------------
>
>                 Key: HDDS-3604
>                 URL: https://issues.apache.org/jira/browse/HDDS-3604
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Vinayakumar B
>            Assignee: Vinayakumar B
>            Priority: Major
>              Labels: pull-request-available
>
> Hadoop-3.3 will be released soon, which brings the most important and long 
> awaited Protobuf upgrade to 3.7, by shading the internal protobuf classes in 
> Hadoop-thirdparty library, still keeping the protobuf-2.5.0 as a transitive 
> dependency.
> Unfortunately, There are direct usages of Hadoop's internal protobuf classes. 
> Because of this, ozone breaks after upgrading hadoop dependency to 3.3.0
> This Jira intends to do avoid such direct usages of hadoop's protobuf classes.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to