[
https://issues.apache.org/jira/browse/HTRACE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943896#comment-14943896
]
Colin Patrick McCabe commented on HTRACE-273:
---------------------------------------------
I thought about this a little more, and I can see a problem with this.
{{htrace-core-3.2.0-incubating.jar}} contains
{{org.apache.htrace.impl.LocalFileSpanReceiver}}, whereas
{{htrace-core4-4.0.1-incubating.jar}} contains
{{org.apache.htrace.core.LocalFileSpanReceiver}}. These two jars may end up on
the same CLASSPATH for something like Hadoop. With this patch, we'll try to
create both span receivers when the short class name is configured. The 3.2.0
version will fail to be constructed, but with an ugly exception.
I think maybe we should just leave the behavior how it is. It does mean that
most users will have to use full class names from now on, but that's probably
OK. In Hadoop, most pluggable classes are configured with full class names and
it seems to work pretty well.
> Add or change default package name of span reciever
> ---------------------------------------------------
>
> Key: HTRACE-273
> URL: https://issues.apache.org/jira/browse/HTRACE-273
> Project: HTrace
> Issue Type: Bug
> Components: core
> Reporter: Masatake Iwasaki
> Assignee: Masatake Iwasaki
> Attachments: HTRACE-273.001.patch
>
>
> If the package name of span receiver is ommitted, {{org.apache.htrace.core}}
> is used as default but only receivers for testing purpose are in the package.
> Practical span receiver implementations are in {{org.apache.htrace.impl}} now.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
