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 2014/12/30 23:00:13 UTC

[jira] [Commented] (HTRACE-31) more JSON serialization fixes

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

stack commented on HTRACE-31:
-----------------------------

+1 Lets get it in.  The way you allocate an ObjectMapper each time we serialize, you might want to change later (its heavyweight instantiating one of those IIRC) but fine for now.

> more JSON serialization fixes
> -----------------------------
>
>                 Key: HTRACE-31
>                 URL: https://issues.apache.org/jira/browse/HTRACE-31
>             Project: HTrace
>          Issue Type: Bug
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>         Attachments: HTRACE-31.001.patch
>
>
> More JSON serialization fixes
> * Do not quote numeric time fields (they should be less than 55 bits)
> * Use jackson for JSON serialization, not an ancient version of jetty
> * Implement JSON deserialization as well as serialization in htrace-core
> * Shorten "time" and "msg" fields to "t" and "m" in TimelineAnnotation
> * fix ToString method that was using "%08x" rather than "%016x"
> * REST methods should take hex values for span IDs, not decimal
> * Add TestMilliSpan to test round-tripping JSON in htrace-core



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)