You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2016/01/12 21:53:39 UTC
[jira] [Moved] (HBASE-15092) HBase personality should order modules
correctly
[ https://issues.apache.org/jira/browse/HBASE-15092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Busbey moved YETUS-279 to HBASE-15092:
-------------------------------------------
Key: HBASE-15092 (was: YETUS-279)
Project: HBase (was: Yetus)
> HBase personality should order modules correctly
> ------------------------------------------------
>
> Key: HBASE-15092
> URL: https://issues.apache.org/jira/browse/HBASE-15092
> Project: HBase
> Issue Type: Bug
> Components: build
> Reporter: Ted Yu
>
> 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):
> {code}
> + void splitRegion(final byte[] regionName, final byte[] splitPoint, final UUID id)
> {code}
> Incorrect order of building the modules led to the following compilation error:
> {code}
> [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)
> {code}
> HBase personality should order the modules according to the Maven dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)