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 Tue, 04 Oct 2016 12:01:20 GMT

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

Weiwei Yang commented on HADOOP-13628:
--------------------------------------

Hello [~liuml07]

Majority of the conflicts is from HADOOP-13588, that one add the support of ACCEPT header
in ConfServlet, but it was only committed to trunk. So we have 2 options here, 

1. Commit HADOOP-13588 to branch-2 and branch-2.7 as well, then this one.
2. Only commit this one to trunk

I am OK with either option, and a little bit prefer to #2, because this ticket was initially
for the development of YARN-5145 and that one is in trunk. Please let me know your option.
Thank you!

> 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, HADOOP-13628.05.patch, HADOOP-13628.06.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