chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Graham (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-515) REST API for Agent
Date Fri, 03 Sep 2010 14:28:33 GMT

    [ https://issues.apache.org/jira/browse/CHUKWA-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905912#action_12905912
] 

Bill Graham commented on CHUKWA-515:
------------------------------------

I personally don't need this feature.  It was included in Eric's original rough spec in the
email chain referenced in CHUKWA-514 which got me thinking about it. Eric, do you need this?
I thought it might be convenient to be able to write to a different cluster, but if it's difficult
to make that happen, I won't be the one to push for this functionality.

> 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
>
> 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.


Mime
View raw message