[
https://issues.apache.org/jira/browse/HTRACE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310347#comment-14310347
]
Colin Patrick McCabe commented on HTRACE-105:
---------------------------------------------
Sounds good to me, except for two things:
* I think we can drop the old vocabulary... we never had a stable release with
it
* We don't use /0xSPAN_ID, we use /SPAN_ID ... we could consider adding the 0x,
but it's not there now. We always identify using hex.
> Cleanup our REST vocabulary supported by htraced
> ------------------------------------------------
>
> Key: HTRACE-105
> URL: https://issues.apache.org/jira/browse/HTRACE-105
> Project: HTrace
> Issue Type: Improvement
> Reporter: stack
>
> Currently, we support the following REST operations:
> {code}
> /0xSOME_SPAN_ID // a GET of a span id will return the span
> /server/info // A GET will return server version, etc.
> /writeSpan // POSTing here will allow you write spans
> /0XSOME_SPAN_ID/children // A GET here will return the children of a span id
> /span/0xSOME_SPAN_ID // A GET here will return a span.
> /query?QUERY_IN_QUERY_STRING // A GET will return result of query
> {code}
> How about we just do:
> /query?.....
> /server/info
> /span/0xSOME_SPAN_ID // A GET here will return a span
> /span // A POST here will allow you write spans
> /span/0xSOME_SPAN_ID/children // A GET here will return children.
> We won't drop the old means. We'll just talk up the above as the canonical
> vocabulary.
> [~eclark] You listening?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
