[
https://issues.apache.org/jira/browse/HTRACE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737863#comment-14737863
]
Masatake Iwasaki commented on HTRACE-114:
-----------------------------------------
bq. 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.
Right. Stub classes is only needed to use MiniHBaseCluster in {{mvn test}}. We
can put both of htrace-core-3.1.0.jar and htrace-core-4.1.0-SNAPSHOT.jar on the
CLASSPATH in normal use cases.
bq.
http://stackoverflow.com/questions/4312553/maven-assembly-add-different-version-of-the-same-artifact
We can put multiple versions in assembled jar by this but the jar is not used
to run {{mvn test}}.
bq. It's not a long-term solution, either, since future versions of hbase will
depend on newer versions of htrace.
Yeah. We can remove them after HBase support htrace-4.
> 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)
