[
https://issues.apache.org/jira/browse/HBASE-25989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-25989.
-----------------------------------
Fix Version/s: 2.4.5
2.5.0
3.0.0-alpha-1
Hadoop Flags: Reviewed
Assignee: Michael Stack
Resolution: Fixed
Pushed to branch-2.4+ Thanks for reviews [~zhangduo] and [~weichiu]
> FanOutOneBlockAsyncDFSOutput using shaded protobuf in hdfs 3.3+
> ---------------------------------------------------------------
>
> Key: HBASE-25989
> URL: https://issues.apache.org/jira/browse/HBASE-25989
> Project: HBase
> Issue Type: Sub-task
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.5
>
>
> The parent added some fancy dancing to make it so on hadoop-3.3.0+ we'd use
> hadoops shaded protobuf rather than the non-relocated protobuf. When hdfs
> 3.3, the 'trick' is not working so we continue to use the unshaded protobuf.
> Fix is trivial.
> Found this testing the 3.3.1RC3. Hard to see because whether we use shaded or
> unshaded is at DEBUG level. If you set DEBUG level and run
> TestFanOutOneBlockAsyncDFSOutput with hdfs 3.3.1 RC candidate in place you'll
> see it uses the unshaded protobuf.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
