Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 20 Sep 2016 16:37:20 +0000 (UTC)
From: "Weiwei Yang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13006232.1474389343000.617313.1474389440586@Atlassian.JIRA>
In-Reply-To: <JIRA.13006232.1474389343000@Atlassian.JIRA>
References: <JIRA.13006232.1474389343000@Atlassian.JIRA> <JIRA.13006232.1474389343797@arcas>
Subject: [jira] [Updated] (HADOOP-13628) Support to retrieve specific
 property from configuration via REST API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 20 Sep 2016 16:37:27 -0000


     [ 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org