[
https://issues.apache.org/jira/browse/HADOOP-13628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated HADOOP-13628:
---------------------------------
Description:
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.
was:
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,
{code}
curl --header "Accept:application/json"
http://${RM_HOST}/conf?name=yarn.nodemanager.aux-services
{"property"{"key":"yarn.resourcemanager.hostname","value":"${RM_HOST}","isFinal":false,"resource":"yarn-site.xml"}}
{code}
This change is fully backwards compatible.
> 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
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
