Bug 756680 - Delete method for package node version histories
Summary: Delete method for package node version histories
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: BRMS 5.2.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Mark Proctor
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-24 09:23 UTC by Toshiya Kobayashi
Modified: 2020-04-27 01:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 958406 (view as bug list)
Environment:
Last Closed:
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GUVNOR-1759 0 Major Resolved Delete method for package node version histories 2015-11-20 10:13:03 UTC

Description Toshiya Kobayashi 2011-11-24 09:23:56 UTC
Version histories of a package node keep growing when you save(check in) a package. Because drools:compiledPackage tends to consume disk space, a delete method for package node version histories is desired.

This is a feature request, not a bug. But I've set the Severity to 'high' as there is no good workaround for it.

The official supported workaround is 'Export repository as xml and import it to BRMS with clean database'. But this will remove version histories of ALL nodes.

The other way is writing your own tool to delete version histories of a package node. But using Drools internal APIs and Jackrabbit APIs is out of support scope.


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