From fd2cfa356c836672e0c49c45952e63b5318b94ac Mon Sep 17 00:00:00 2001 From: Yanming Zhou Date: Fri, 23 Feb 2018 11:23:23 +0800 Subject: [PATCH] Change start-limit to match example playerSummarization is not started in Run 3. --- spring-batch-docs/asciidoc/step.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/spring-batch-docs/asciidoc/step.adoc b/spring-batch-docs/asciidoc/step.adoc index 034af860b..af648dacd 100644 --- a/spring-batch-docs/asciidoc/step.adoc +++ b/spring-batch-docs/asciidoc/step.adoc @@ -432,7 +432,7 @@ The following example shows how to configure a job to have steps that can be res - + @@ -475,7 +475,7 @@ public Step gameLoad() { @Bean public Step playerSummarization() { return this.stepBuilderFactor.get("playerSummarization") - .startLimit(3) + .startLimit(2) .chunk(10) .reader(playerSummarizationSource()) .writer(summaryWriter()) @@ -497,7 +497,7 @@ every time in case extra files have been added since it last ran. It has 'allow-start-if-complete' set to 'true' in order to always be started. (It is assumed that the database tables games are loaded into has a process indicator on it, to ensure new games can be properly found by the summarization step). The summarization step, -which is the most important in the job, is configured to have a start limit of 3. This +which is the most important in the job, is configured to have a start limit of 2. This is useful because if the step continually fails, a new exit code is returned to the operators that control job execution, and it can not start again until manual intervention has taken place.