[
https://issues.apache.org/jira/browse/AMBARI-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171836#comment-15171836
]
Hadoop QA commented on AMBARI-15133:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12790460/AMBARI-15133.v10.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5609//console
This message is automatically generated.
> Functionality to purge operational logs from the ambari database
> ----------------------------------------------------------------
>
> Key: AMBARI-15133
> URL: https://issues.apache.org/jira/browse/AMBARI-15133
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
> Affects Versions: 2.2.1
> Reporter: Laszlo Puskas
> Assignee: Laszlo Puskas
> Labels: features
> Fix For: 2.2.2
>
> Attachments: AMBARI-15133.v10.patch, AMBARI-15133.v5.patch,
> AMBARI-15133.v8.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Ambari operational data may significantly grow over time and as a result the
> database operations may degrade.
> This feature is about allowing operators to purge related tables based on
> configurable cleaning policies. (As a first step only time based cleanup is
> to be supported)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
