[#BATCH-231] Chunk completion policy

Spring Batch

BATCH-220

Chunk completion policy

Created: 29/Nov/07 07:52 AM Updated: 07/Aug/08 10:06 AM

Component/s:

None

Affects Version/s:

1.0-m3

Fix Version/s:

1.1.0

Security Level:

Public (Public Issues)

Time Tracking:

Original Estimate:

Remaining Estimate:

Time Spent:

Not Specified

Description

« Hide

SpepCompletionPolicy and implementations. A step can complete based on data exhaustion (no more chunks) or abnormally based on information the StepExecutor / ChunkProvider gets from the ChunkExecutor. See ~~BATCH-225~~ for details of what information will be available. Up to 1.0-m3 this decision was taken by the StepOperations CompletionPolicy, and actually that is probably a good place for it still to reside - the CompletionPolicy controls the data that it needs in its RepeatContext. Look at existing implementations of CompletionPolicy to understand the pattern.

All

Comments

Work Log

Change History

FishEye

Builds

Sort Order:

[ Permlink | « Hide ]

Lucas Ward added a comment - 25/Feb/08 12:20 PM

I'm not sure I agree with this issue. I think the StepinterruptionPolicy covers part of this requirement in a much better way. The only other issue is that of varying the 'chunk size' which I still feel should be a separate policy. Unless someone disagrees, I'll close as won't fix tomorrow.

[ Permlink | « Hide ]

Lucas Ward added a comment - 02/Mar/08 11:24 PM

We probably want to readdress the issue of how to vary the 'chunk size' dynamically, however, I think it can be pushed back to post- release 1.

[ Permlink | « Hide ]

Dave Syer added a comment - 03/Mar/08 03:14 AM

The new approach that is emerging from ~~BATCH-404~~ means that this can easily be addressed by a factory bean. I added a RepeatOperationsStepFactoryBean to support this use case.

[ Permlink | « Hide ]

Dave Syer added a comment - 07/Aug/08 10:06 AM

Assume closed as resolved and released