[ https://issues.apache.org/jira/browse/OOZIE-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764897#comment-16764897 ]
Andras Salamon commented on OOZIE-3408: --------------------------------------- Thanks for the tip [~andras.piros] It seems to me we already set this property to [50|https://github.com/apache/oozie/blob/master/core/src/main/resources/META-INF/persistence.xml#L76]. I've tried changing the value (0, 1, 1000, ...) but the speed was the same. I'll also test it using [JPAService.executeBatchInsertUpdateDelete|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/JPAService.java#L488], it might be better. > Create new unit test class for PurgeXCommand > -------------------------------------------- > > Key: OOZIE-3408 > URL: https://issues.apache.org/jira/browse/OOZIE-3408 > Project: Oozie > Issue Type: Sub-task > Components: tests > Reporter: Andras Salamon > Assignee: Andras Salamon > Priority: Major > > There is one unit test class for {{PurgeXCommand}}, {{TestPurgeXCommand}} > which needs to be cleaned up. This class tests the selection of the purgeable > records. Most of the test cases are rather small, only a few workflows, > coordinators, bundles have to be checked. > It is also very important that purge service works correctly if large number > of records has to be checked. Purge service should not only select the > purgeable records correctly, it has to do that in a fast and memory efficient > ways. > Since {{TestPurgeXCommand}} is already very large, a new class should be > introduced to contain these tests. Probably the two classes will have a > common superclass. -- This message was sent by Atlassian JIRA (v7.6.3#76005)