[
https://issues.apache.org/jira/browse/AMBARI-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175119#comment-15175119
]
Sebastian Toader commented on AMBARI-15133:
-------------------------------------------
[~u39kun] which files were you seeing causing rat failure? All files in this
patch looks good to me. I also ran mvn clean apache-rat:check for ambari-server
(the patch changes files only within ambari-server) and it's clean:
*branch-2.2*:
{code}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 4055 licence.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
{code}
*trunk*
{code}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 4239 licence.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
{code}
> 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.v12.patch, AMBARI-15133.v2.2.1.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)
