[
https://issues.apache.org/jira/browse/HTRACE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HTRACE-105:
-------------------------
Attachment: 105.txt
Changes /writeSpans POST to /span POST
In htraced, beefed up the help output with REST examples.
Changed the supported REST removing /writeSpans and GET
against / of a span id. Instead, to write, you POST to
/span. You then GET against /span/ID, etc.
Removed PathPrefix("/span"). Couldn't make POST and GET
on same path work.
In htrace client, small edit of usage.
In java REST client, changes to match new REST paths.
Also 'fixed' an overwrite issue if doing many span POSTs
at a time.
> 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
> 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)
