-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
False
-
NEW
-
NEW
-
Undefined
-
---
-
---
-
-
2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15)
When there are a huge number of rows to clean and an error happens during this process, as the LogCleanupCommand run into a transaction, then a rollback is run.
In order to solve this, we are going to add the number of rows to delete as a parameter in the LogCleanupCommand. Then depending on the rest of parameters, all the rows will be removed in packages of rows given by that parameter where each action will be done in a different commit. So the rollback action will be avoid for all the removing request.
- is related to
-
JBPM-10010 Mechanism for housekeeping means RecordsPerTransaction is limited to 1000 on Oracle, unnecessarily
- Open