Hi, I have a project that has a dependency on hbase-mapreduce (2.4.9), which in turn depends on hbase-hadoop2-compat. The latter doesn’t have any version specified for hadoop-mapreduce-client-core and ends up pulling 2.10.0, which conflicts with the Hadoop version I’m running against (3.3.1). What’s the correct way to force hadoop-mapreduce to work with Hadoop 3.3.1? I tried using profiles but I couldn’t get it to work, I wonder if it has anything to do with this change <https://issues.apache.org/jira/browse/HBASE-24309>:
commit dc2146069cd5ef6120f0a9d1918acba0f74ac5c3 Author: Duo Zhang <zhang...@apache.org> Date: Wed May 13 17:59:21 2020 +0800 HBASE-24309 Avoid introducing log4j and slf4j-log4j dependencies for … (#1697) Signed-off-by: stack <st...@apache.org> diff --git a/hbase-hadoop2-compat/pom.xml b/hbase-hadoop2-compat/pom.xml index 236b52ce65..96472fb8f3 100644 --- a/hbase-hadoop2-compat/pom.xml +++ b/hbase-hadoop2-compat/pom.xml @@ -118,14 +118,12 @@ limitations under the License. <dependency> <groupId>org.apache.hbase</groupId> <artifactId>hbase-hadoop-compat</artifactId> - <version>${project.version}</version> <type>test-jar</type> <scope>test</scope> </dependency> <dependency> <groupId>org.apache.hadoop</groupId> <artifactId>hadoop-mapreduce-client-core</artifactId> - <version>${hadoop.version}</version> <exclusions> <exclusion> <groupId>com.google.guava</groupId> Thanks, Giuseppe