[ 
https://issues.apache.org/jira/browse/HTRACE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956141#comment-14956141
 ] 

Hudson commented on HTRACE-279:
-------------------------------

SUCCESS: Integrated in HTrace-Master #130 (See 
[https://builds.apache.org/job/HTrace-Master/130/])
HTRACE-279. Fix issues where the HTracedSpanReceiver was using the wrong 
(cmccabe: rev 157c20ae67a81cf03812a33daff7d8e35c97c354)
* htrace-htraced/src/main/java/org/apache/htrace/impl/RestBufferManager.java
* htrace-htraced/go/src/org/apache/htrace/htraced/rest.go


> 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
>          Components: htraced
>    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)

Reply via email to