hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HADOOP-13628) Support to retrieve specific property from configuration via REST API
Date Wed, 21 Sep 2016 10:22:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15508461#comment-15508461
] 

Weiwei Yang edited comment on HADOOP-13628 at 9/21/16 10:21 AM:
----------------------------------------------------------------

Hi [~steve_l]

Thank you for the comments. 

bq. Does it return the fully evaluated config?

Yes it does.

bq. <pre> blocks

Thanks will do that.

bq. Unknown properties should return 404

That makes sense, will do that

bq. Could we have a text/plain one which returns just the text value?

I am a little hesitated to do that, I did not see any place else that supports to return plain
text, we'd better keep consistency, what do you say?

bq. Presumably a MiniHDFS cluster serves up this data and would respond to a few Jersey requests?

I will add some more tests in {{TestConfServlet}} to verify http responses for both json an
xml format. I will try to mock http requests instead of using mini cluster, hopefully that
will be better.


was (Author: cheersyang):
Hi [~steve_l]

Thank you for the comments. 

bq. Does it return the fully evaluated config?

Yes it does.

bq. <pre> blocks

Thanks will do that.

bq. Unknown properties should return 404

That makes sense, will do that

bq. Could we have a text/plain one which returns just the text value?

I am a little hesitated to do that, I did not see any place else that supports to return plain
text, we'd better keep consistency, what do you say?

bq. Presumably a MiniHDFS cluster serves up this data and would respond to a few Jersey requests?

Is this truly necessary ? The tests in {{TestConfiguration}} should cover all the possible
scenarios of requests. The {{ConfServlet}} simply parse the parameter, call the method then
return the message. The coverage looks enough to me, unless you have more concern.

> Support to retrieve specific property from configuration via REST API
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-13628
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13628
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>    Affects Versions: 2.7.3
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>         Attachments: HADOOP-13628.01.patch, HADOOP-13628.02.patch
>
>
> Currently we can use rest API to retrieve all configuration properties per daemon, but
unable to get a specific property by name. This causes extra parse work at client side when
dealing with Hadoop configurations, and also it's quite over head to send all configuration
in a http response over network. Propose to support following a {{name}} parameter in the
http request, by issuing
> {code}
> curl --header "Accept:application/json" http://${RM_HOST}/conf?name=yarn.nodemanager.aux-services
> {code}
> get output
> {code}
> {"property"{"key":"yarn.resourcemanager.hostname","value":"${RM_HOST}","isFinal":false,"resource":"yarn-site.xml"}}
> {code}
> This change is fully backwards compatible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message