Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 2 May 2013 05:42:16 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12645748.1367472146566.259091.1367473336964@arcas>
In-Reply-To: <JIRA.12645748.1367472146566@arcas>
References: <JIRA.12645748.1367472146566@arcas>
Subject: [jira] [Updated] (HBASE-8479) AggregationClient breaks bigtop
 compile
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-8479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-8479:
-------------------------

    Attachment: 8479_tmp_rm_of_aggregationclient.txt

Patch that temporarily removes aggregation client code.  Going to commit to 0.95 to verify this indeed is all that we need to fix to get the bigtop ci working.  Will put back later after we figure what is up.
                
> AggregationClient breaks bigtop compile
> ---------------------------------------
>
>                 Key: HBASE-8479
>                 URL: https://issues.apache.org/jira/browse/HBASE-8479
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.95.1
>            Reporter: stack
>            Priority: Critical
>             Fix For: 0.95.1
>
>         Attachments: 8479_tmp_rm_of_aggregationclient.txt, attempt1.txt
>
>
> With Roman, am trying to set up a bigtop ci of hbase 0.95 only we fail to compile.  It is the exotic generics that are going on over in AggregateClient.  Here is how we fail:
> {code}
> [ERROR] COMPILATION ERROR : 
> [INFO] -------------------------------------------------------------
> [ERROR] /mnt/jenkins/workspace/HBase-0.95/label/centos6/build/hbase/rpm/BUILD/hbase-0.95-SNAPSHOT/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/AggregationClient.java:[135,59] type parameters of <T>T cannot be determined; no unique maximal instance exists for type variable T with upper bounds Q,com.google.protobuf.Message
> [ERROR] /mnt/jenkins/workspace/HBase-0.95/label/centos6/build/hbase/rpm/BUILD/hbase-0.95-SNAPSHOT/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/AggregationClient.java:[208,59] type parameters of <T>T cannot be determined; no unique maximal instance exists for type variable T with upper bounds Q,com.google.protobuf.Message
> [ERROR] /mnt/jenkins/workspace/HBase-0.95/label/centos6/build/hbase/rpm/BUILD/hbase-0.95-SNAPSHOT/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/AggregationClient.java:[328,57] type parameters of <T>T cannot be determined; no unique maximal instance exists for type variable T with upper bounds T,com.google.protobuf.Message
> [ERROR] /mnt/jenkins/workspace/HBase-0.95/label/centos6/build/hbase/rpm/BUILD/hbase-0.95-SNAPSHOT/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/AggregationClient.java:[390,57] type parameters of <T>T cannot be determined; no unique maximal instance exists for type variable T with upper bounds T,com.google.protobuf.Message
> [ERROR] /mnt/jenkins/workspace/HBase-0.95/label/centos6/build/hbase/rpm/BUILD/hbase-0.95-SNAPSHOT/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/AggregationClient.java:[489,59] type parameters of <T>T cannot be determined; no unique maximal instance exists for type variable T with upper bounds T,com.google.protobuf.Message
> [ERROR] /mnt/jenkins/workspace/HBase-0.95/label/centos6/build/hbase/rpm/BUILD/hbase-0.95-SNAPSHOT/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/AggregationClient.java:[591,59] type parameters of <T>T cannot be determined; no unique maximal instance exists for type variable T with upper bounds T,com.google.protobuf.Message
> [INFO] 6 errors 
> {code}
> I cannot reproduce locally but googling, I see that above is pretty common complaint when you move between compilers.  Various are the recommendations for fix but none definitive.  The easiest is dumbing down the generics which I tried but it only caused issues in other coprocessors.
> If clues on how to fix this, I'm all ears.  Would like to get this bigtop ci build running.  Its cool.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira