Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
Description
See the thread on dev@yetus, 'determining cause for compilation error'.
In HBASE-15075, I modify class SplitNormalizationPlan.java in hbase-server module which calls the following new method added to Admin.java (in hbase-client module):
+ void splitRegion(final byte[] regionName, final byte[] splitPoint, final UUID id)
Incorrect order of building the modules led to the following compilation error:
[ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /testptch/hbase/hbase-server/src/main/java/org/apache/hadoop/hbase/master/normalizer/SplitNormalizationPlan.java:[95,12] no suitable method found for splitRegion(byte[],byte[],java.util.UUID) method org.apache.hadoop.hbase.client.Admin.splitRegion(byte[]) is not applicable (actual and formal argument lists differ in length) method org.apache.hadoop.hbase.client.Admin.splitRegion(byte[],byte[]) is not applicable (actual and formal argument lists differ in length)
HBase personality should order the modules according to the Maven dependencies.