Bug 1145776 - RHQ_PARTITION_EVENT data not purged automatically
Summary: RHQ_PARTITION_EVENT data not purged automatically
Status: ON_QA
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server, Database
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
: RHQ 4.13
Assignee: Thomas Segismont
QA Contact: Mike Foley
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-23 18:00 UTC by Elias Ross
Modified: 2016-05-24 10:19 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed:


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 1297702 None None None Never

Internal Trackers: 1297702

Description Elias Ross 2014-09-23 18:00:59 UTC
Description of problem:

I have 3 million rows in the RHQ_PARTITION_EVENT table. No need for this data after a few weeks I would think.


Version-Release number of selected component (if applicable): 4.12

Comment 1 Elias Ross 2014-09-23 18:03:25 UTC
Also RHQ_PARTITION_DETAILS as well. I have 300,000 rows here.

Comment 2 Thomas Segismont 2014-10-16 12:33:59 UTC
Pull request sent and waiting for review:
https://github.com/rhq-project/rhq/pull/132

Comment 3 Thomas Segismont 2014-11-20 09:35:53 UTC
Merged in master

commit 8efb4f275b98d85a8bee2f12110dd955a1ebf67c
Merge: 86968f0 1f08ab3
Author: Libor Zoubek <lzoubek@redhat.com>
Date:   Thu Nov 13 18:16:58 2014 +0100

    Merge branch 'purgepurgepurge' of https://github.com/tsegismont/rhq into tsegismont-purgepurgepurge
    
    Conflicts:
        modules/core/dbutils/src/main/scripts/dbupgrade/db-upgrade.xml
        modules/enterprise/gui/coregui/src/main/resources/org/rhq/coregui/client/Messages_de.properties
        modules/enterprise/gui/coregui/src/main/resources/org/rhq/coregui/client/Messages_ja.properties
        modules/enterprise/gui/coregui/src/main/resources/org/rhq/coregui/client/Messages_ru.properties


Note You need to log in before you can comment on or make changes to this bug.