[
https://issues.apache.org/jira/browse/HTRACE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312685#comment-14312685
]
Colin Patrick McCabe commented on HTRACE-105:
---------------------------------------------
This looks good. Thanks, Stack. The fix for the htraced java client looks
good.
Can we move the REST documentation into a REST.txt file or similar? It just
feels a bit awkward to have it in the usage message for the {{htraced}}
daemon-- most of the time, people asking for daemon usage want to know how to
run the daemon, not how to communicate with it, I think. It's kind of a
programmer thing, not a user thing.
We maybe could have a {{\-\-rest-help}} switch if it really, absolutely has to
be in the binary... but a REST.txt seems pretty good... If we had a REST.txt,
we could also add on to it later with addition details about span JSON and etc.
> 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
> Assignee: stack
> Attachments: 105.txt
>
>
> 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)
