Thanks for the update Wei-Chiu and Gabor. Seems like some necessary "paving" to >Hadoop-3.1 that you're doing.
Am watching 22087 now. On 3/22/19 10:56 AM, Wei-Chiu Chuang wrote:
I filed HBASE-22087 <https://issues.apache.org/jira/browse/HBASE-22087>, and am working on a patch to address this. For supported Hadoop version, check out the HBase reference guide: http://hbase.apache.org/book.html#hadoop The latest Hadoop release, 3.2.0, is not yet tested. On Fri, Mar 22, 2019 at 3:26 PM Gabor Bota <gabor.b...@cloudera.com.invalid> wrote:Hi HBase Devs, Task I'm working on *HADOOP-15960. Update guava to 27.0-jre* in hadoop-common from version 11.0.2. After a successful hadoop build with my patch, I wanted to run the hbase integration tests with the updated guava in hadoop. After my attempt was not successful I tried to run the build with the 3.3.0-SNAPSHOT without any modification but I got similar issues. Issues [WARNING] Rule 0: org.apache.maven.plugins.enforcer.EvaluateBeanshell failed with message: License errors detected, for more detail find ERROR in /Users/gaborbota/dev/hbase/hbase-shaded/hbase-shaded-mapreduce/target/maven-shared-archive-resources/META-INF/LICENSE The error is the following in the LICENSE file: - This product includes JLine Bundle licensed under the The BSD License Yes, this is "the The BSD License". The issue is with the following dependency: <groupId>org.jline</groupId> <artifactId>jline</artifactId> <version>3.9.0</version> ======== After skipping check-aggregate-license from the execution, the build fails on hbase-shaded-check-invariants module. The issue is the following: Found artifact with unexpected contents: '/Users/gaborbota/dev/hbase/hbase-shaded/hbase-shaded-client-byo-hadoop/target/hbase-shaded-client-byo-hadoop-3.0.0-SNAPSHOT.jar' The full log of unexpected paths: https://gist.github.com/bgaborg/e71fd2daef6ff3bf06254a62ae8f7d03 Questions - What is the latest hadoop version that is tried and working with hbase? - Do you plan to support the latest version? - Do you have an active ongoing jira with these errors? Thanks, Gabor
