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

Hadoop QA commented on AMBARI-10658:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12727237/AMBARI-10658.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2461//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2461//console

This message is automatically generated.

> Refactor stack-config's 'property_depended_by' information into a sub-resource
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-10658
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10658
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10658.patch
>
>
> Currently the {{property_depended_by}} information for a stack-configuration 
> is calculated automatically. This has to be changed so that the derived 
> information can be got through a sub-resource called dependencies. This will 
> contain the same information as the configuration does currently.
> So a GET to 
> [http://c6401:8080/api/v1/stacks/HDP/versions/2.2/services/YARN/configurations/yarn.scheduler.maximum-allocation-mb/dependencies]
>  will give
> {code}
> {
>     "property_depended_by" : [
>       {
>         "type" : "mapred-site",
>         "name" : "yarn.app.mapreduce.am.resource.mb"
>       },
>       {
>         "type" : "mapred-site",
>         "name" : "mapreduce.map.memory.mb"
>       },
>       {
>         "type" : "mapred-site",
>         "name" : "mapreduce.reduce.memory.mb"
>       }
>     ]
> }
> {code}
> Additionally there should be a single API to get all the configurations, and 
> all their depended_by relationship sub-resources. Currently the UI calls: 
> {code}
> http://c6401:8080/api/v1/stacks/HDP/versions/2.3/services?StackServices/service_name.in(HDFS,MAPREDUCE2,YARN,TEZ,HIVE,HBASE,PIG,ZOOKEEPER)
> &fields=configurations/*,StackServices/config_types/*
> {code}
> We should have something very similar like
> {code}
> http://c6401:8080/api/v1/stacks/HDP/versions/2.3/services?StackServices/service_name.in(HDFS,MAPREDUCE2,YARN,TEZ,HIVE,HBASE,PIG,ZOOKEEPER)
> &fields=configurations/*,configurations/dependencies,StackServices/config_types/*
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to