You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@htrace.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/10/14 00:37:05 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14955838#comment-14955838 ] 

stack commented on HTRACE-279:
------------------------------

+1

> 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
>         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)