chunk-oriented-processing and completion-policy inconsistent with documentation

[spring-projects-issues]

Jimmy Praet opened BATCH-1967 and commented

https://docs.spring.io/spring-batch/docs/current/reference/html/index-single.html#chunkOrientedProcessing
https://docs.spring.io/spring-batch/docs/current/reference/html/index-single.html#stoppingAJobManuallyForBusinessReasons

According to the documentation chunk-oriented-processing has a (read+process) loop until the completion-policy is reached, and then the chunk is handed to the ItemWriter. In actuality it is a read-loop until the completion-policy is reached (ChunkProvider), and then the chunk is handed to the ChunkProcessor that has a process-loop after which the chunk is handed to the ItemWriter.

This means it is not possible to use a completion-policy to for example commit your chunk after 100 records are processed, or 1 minute has passed (whichever comes first).

---

Reference URL: http://forum.springsource.org/showthread.php?116507-chunk-completion-policy

2 votes, 2 watchers

[spring-projects-issues]

Jimmy Praet commented

Section "11.10 Chunk with Custom Checkpoint Processing" of JSR 352 also describes a read+process loop until the commit criteria of the CheckpointAlgorithm is reached.

[spring-projects-issues]

Alexis SOUMAGNE commented

Good to know I'm not the only one thinking in the same way.

[tomasz-belina-nes]

What are the plans related to this issue ?

[fmbenhassine]

I just planned this issue to be included in the next release.

[tomasz-belina-nes]

I just planned this issue to be included in the next release.

Documentation will be updated or behavior will be changed ?