You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@htrace.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2015/10/14 01:09:05 UTC
[jira] [Resolved] (HTRACE-279) Fix issues where the
HTracedSpanReceiver was using the wrong JSON serialization for spans and
add validation to htraced REST ingest path
[ https://issues.apache.org/jira/browse/HTRACE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin Patrick McCabe resolved HTRACE-279.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 4.1
committed to 4.1, thanks
> Fix issues where the HTracedSpanReceiver was using the wrong JSON serialization for spans 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
> Fix For: 4.1
>
> Attachments: HTRACE-279.001.patch
>
>
> 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)