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

Steve Loughran commented on HADOOP-13628:
-----------------------------------------

# go on, support text/plain too :)
# when there's a 404, what content type comes back? I ask as there's aways the 
risk that bad client code will fail badly trying to parse the HTML, without 
looking at the status code. As long as text/html comes back, we get to deny all 
responsibility

> 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, 
> HADOOP-13628.03.patch, HADOOP-13628.04.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to