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] [Commented] (HADOOP-13628) Support to retrieve specific property from configuration via REST API
Date Thu, 22 Sep 2016 14:38:20 GMT

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

Weiwei Yang commented on HADOOP-13628:

Hello [~stevel@apache.org]

# I have created HADOOP-13639 for the plain text stuff.
# For the 404 error, use following command

curl --header "Accept:application/json" http://deale1.fyre.ibm.com:8088/conf?name=xxx

you will get following output

<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 404 Property xxx not found</title>
<body><h2>HTTP ERROR 404</h2>
<p>Problem accessing /conf. Reason:
<pre>    Property xxx not found</pre></p><hr /><i><small>Powered
by Jetty://</small></i><br/>

from browser, you'll get error like screen shot [^404_error_browser.png]

> 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: 404_error_browser.png, 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

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

View raw message