[
https://issues.apache.org/jira/browse/AMBARI-20559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940435#comment-15940435
]
Hadoop QA commented on AMBARI-20559:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12860347/AMBARI-20559.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 2 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-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11163//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11163//console
This message is automatically generated.
> Create a base class for caching in ambari-agent.
> ------------------------------------------------
>
> Key: AMBARI-20559
> URL: https://issues.apache.org/jira/browse/AMBARI-20559
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20559.patch
>
>
> The class should be:
> 1\. Thread-safe
> 2\. Support caching for multiple clusters
> 3\. Write cache to json file for debug purposes.
> In next jiras the class with be derived by ClusterConfigurationCache,
> ClusterTopologyCache and ClusterComponentsStatusCache.
> We have already a caching class for alerts. The jira should also rewrite it to
> use the base class.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
