[
https://issues.apache.org/jira/browse/HTRACE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737395#comment-14737395
]
Colin Patrick McCabe commented on HTRACE-114:
---------------------------------------------
[~stack]: I think the issue here is that hbase 1.0.0 requires the symbols
provided by htrace-core 3.1.0. Maven refuses to put two different versions of
something on the classpath (at least in this case) and so strips out the
htrace-core 3.1.0 dependency in favor of htrace-core 4.1.0-SNAPSHOT, which does
not provide the symbols hbase 1.0.0 needs.
[~iwasakims]: I really would rather not add all these old class names. It's a
big mess. It's not a long-term solution, either, since future versions of
hbase will depend on newer versions of htrace.
I think one solution is to get Maven to put htrace-core-3.1.0.jar on the
CLASSPATH alongside htrace-core-4.1.0-SNAPSHOT.jar. There are some techniques
discussed here:
http://stackoverflow.com/questions/4312553/maven-assembly-add-different-version-of-the-same-artifact
If worst comes to worst, we can just run a (secure) wget to the CLASSPATH in
an ant task. We know exactly which version we need for hbase-1.0.0.
The other potential solution here is to wait until a new version of hbase is
released that uses htrace-4.0.
I'd also like to note that this is not a problem in production, since in
production we can just drop the htrace-hbase jar on the HBase CLASSPATH and all
will be well. The problem is just getting Maven to do what we want in our unit
tests and htrace build.
> Fix compilation error of htrace-hbase against hbase-1.0.0
> ---------------------------------------------------------
>
> Key: HTRACE-114
> URL: https://issues.apache.org/jira/browse/HTRACE-114
> Project: HTrace
> Issue Type: Bug
> Affects Versions: master
> Reporter: Masatake Iwasaki
> Assignee: Masatake Iwasaki
> Attachments: HTRACE-114.001.patch, HTRACE-114.002.patch
>
>
> HBaseSpanReceiver uses Table#flushCommits which is removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
