[
https://issues.apache.org/jira/browse/AMBARI-8959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261194#comment-14261194
]
Hadoop QA commented on AMBARI-8959:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12689516/AMBARI-8959.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{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:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1125//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1125//console
This message is automatically generated.
> UI uses old sub-resource names for API requests to /stacks/
> -----------------------------------------------------------
>
> Key: AMBARI-8959
> URL: https://issues.apache.org/jira/browse/AMBARI-8959
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8959.patch
>
>
> BE contains a hotfix for renaming old-style subresource names to new ones:
> "stackServices" -> "services"
> "serviceComponents" -> "components"
> "operatingSystems" -> "operating_systems"
> The logic for the replacement is `if href contains /stacks/ and not contains
> _=`, so it returns `operating_systems` for regular requests and
> `operatingSystems` for requests from UI, as all of them contain cache busters.
> UI should use new names everywhere; after that it would be possible to remove
> the hotfix from BE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)