[
https://issues.apache.org/jira/browse/CHUKWA-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908407#action_12908407
]
Eric Yang commented on CHUKWA-515:
----------------------------------
Minor issues:
1. The POST command does not return the adaptor ID. It should return the ID
for remote side to track the adaptor.
2. The AdaptorServlet implemented REST api from scratch. It would be nice if
it uses Jersey style of rest api. I ran into a problem with Content-Type:
application/json. My Firefox REST Client is adding charset after Content-Type.
ie.
{noformat}
Conten-Type: application/json; charset=UTF-8
{noformat}
AdaptorServlet choke on the charset addition.
3. Using jersey style REST API, it would be easier to manage rpc data structure
versioning, and support multiple serialization format (xml, json, protocol
buffer, avro, etc).
> REST API for Agent
> ------------------
>
> Key: CHUKWA-515
> URL: https://issues.apache.org/jira/browse/CHUKWA-515
> Project: Chukwa
> Issue Type: Sub-task
> Components: data collection
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: CHUKWA-515-1.patch, CHUKWA-515-2.patch
>
>
> Develop a REST interface for the Agent to expose Adaptor CRUD operations.
> * Request URI:
> {noformat}
> GET /rest/v1/adaptor HTTP/1.0
> {noformat}
> * For now I'm shooting for the XML and plain text response, but ultimately we
> can support optional params:
> {noformat}
> viewType=[json|xml|text] (default is XML?)
> {noformat}
> I'm planning on using Jetty similar to how the collector does. We could have
> some common code that delegates requests to different handlers based on the
> URI. The current telnet interface will remain as-is.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
