[ 
https://issues.apache.org/jira/browse/HBASE-12236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174233#comment-14174233
 ] 

Masatake Iwasaki commented on HBASE-12236:
------------------------------------------

The problem is that hbase-0.98 is built against htrace-2.04 which is old. I 
think it is good to bump the version of htrace from 2.04 to 3.0.4 as attached 
patch do though bumping the version of htrace is incompatible change in the 
sense that user need to change the value of hbase.trace.spanreceiver.classes 
from org.cloudera.htrace.impl.* to org.htrace.impl.*.

htrace-zipkin-2.04 and htrace-zipkin-3.0.4 are compatible in the sense that
* htrace-2.04 and htrace-3.0.4 has same data structure for tracing span
* htrace-zipkin-2.04 and htrace-zipkin-3.0.4 uses same Zipkin client API

Even if the version of htrace is bumped, htrace-hbase still does not work with 
hbase-0.98 because it depends on o.a.h.http.HttpServer2 which does not exist in 
hadoop-2.2.0 but this is another issue.


> Change namespace of HTraceConfiguration dependency in 0.98
> ----------------------------------------------------------
>
>                 Key: HBASE-12236
>                 URL: https://issues.apache.org/jira/browse/HBASE-12236
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 12236-v1.txt
>
>
> As discussed in thread 'NoSuchMethodError using zipkin with hbase 0.98.5', 
> HBaseSpanReceiver.config() method from htrace-hbase module expects parameter 
> of type org.htrace.HTraceConfiguration.
> However, org.apache.hadoop.hbase.trace.HBaseHTraceConfiguration in 0.98 
> extends org.cloudera.htrace.HTraceConfiguration , leading to the following 
> compilation error when building htrace-hbase against 0.98:
> {code}
> [ERROR]
> /home/hadoop/git/htrace/htrace-hbase/src/main/java/org/htrace/impl/HBaseSpanReceiver.java:[341,12]
> error: method configure in class HBaseSpanReceiver cannot be applied to
> given types;
> {code}
> Thanks to Abhishek Kumar who reported the above issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to