You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by ud...@apache.org on 2022/07/20 21:09:51 UTC

[hudi] branch master updated: [HUDI-4401] Skip HBase version check (#6114)

This is an automated email from the ASF dual-hosted git repository.

uditme pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hudi.git


The following commit(s) were added to refs/heads/master by this push:
     new 2b828ccb98 [HUDI-4401] Skip HBase version check (#6114)
2b828ccb98 is described below

commit 2b828ccb98b48f122f2fcc5c268b8e2bf8fd8854
Author: Y Ethan Guo <et...@gmail.com>
AuthorDate: Wed Jul 20 14:09:45 2022 -0700

    [HUDI-4401] Skip HBase version check (#6114)
---
 hudi-common/src/main/resources/hbase-site.xml | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/hudi-common/src/main/resources/hbase-site.xml b/hudi-common/src/main/resources/hbase-site.xml
index ad680e6b89..3722cae18e 100644
--- a/hudi-common/src/main/resources/hbase-site.xml
+++ b/hudi-common/src/main/resources/hbase-site.xml
@@ -37,6 +37,13 @@ HBaseConfiguration::addHbaseResources().  To get around this issue,
 since HBase loads "hbase-site.xml" after "hbase-default.xml", we
 provide hbase-site.xml from the bundle so that HBaseConfiguration
 can pick it up and ensure the right defaults.
+
+The HBase version check is skipped (setting "hbase.defaults.for.version.skip"
+to true instead of false as default) to avoid any inconvenience caused
+by the RuntimeException due to version mismatch if multiple versions
+of HBase library are present in the class path.  In such a case, the
+user needs to make sure there is no config conflict between different
+versions.
 -->
 
 <!--
@@ -1427,7 +1434,7 @@ possible configurations would overwhelm and obscure the important.
   </property>
   <property>
     <name>hbase.defaults.for.version.skip</name>
-    <value>false</value>
+    <value>true</value>
     <description>Set to true to skip the 'hbase.defaults.for.version' check.
       Setting this to true can be useful in contexts other than
       the other side of a maven generation; i.e. running in an