[
https://issues.apache.org/jira/browse/HTRACE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955800#comment-14955800
]
Colin Patrick McCabe commented on HTRACE-279:
---------------------------------------------
P.S. There's a little more info on custom serializers here:
http://wiki.fasterxml.com/JacksonHowToCustomSerializers
However, I can't find any explanation for why the \@JsonSerializer annotation
sometimes works and sometimes not.
> Force HTraced span receiver to use SpanSerializer and add validation to
> htraced REST ingest path
> ------------------------------------------------------------------------------------------------
>
> Key: HTRACE-279
> URL: https://issues.apache.org/jira/browse/HTRACE-279
> Project: HTrace
> Issue Type: Bug
> Affects Versions: 4.1
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
>
> Apparently the HTracedReceiver is sometimes not using the JSON SpanSerializer
> from htrace-core4. We should force the span receiver to use that serializer.
> Also, we should add span ID validation to the htraced daemon. Currently, a
> bad span ID can crash the daemon, which is not very robust. These changes
> will fix the unit test failure in TestHTracedReceiver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
