-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proper default value for skipLimit #4661
Comments
That's a valid point, thank you for raising it!
This means that by default we would theoretically allow the entire dataset to be skipped, which in turn means there is something fundamentally wrong with the input (bad data format, unexpected input, etc). As a user, I would prefer my job to fail fast in the first dozen or hundred skips rather than waiting until the end just to discover that my job was skipping the entire data set. Do you see my point? I guess 10 or 100 is a reasonable default. Wdyt? I will plan the change in the next minor release. |
Hi @fmbenhassine, |
I have opened a pull request that addresses this issue: #4668 |
Resolves spring-projects#4661 Signed-off-by: Fabrice Bibonne <[email protected]>
Before this commit, an assertion was enforcing that when a skip limit is provided, then at least one skippable exception is defined. Since the default value of skip limit was changed to 10 in fd45d32, that assertion is now replaced with a log message at debug level. Related to spring-projects#4661 Signed-off-by: Fabrice Bibonne <[email protected]>
Recently I stumbled over the default value of the skipLimit in the class FaultTolerantStepBuilder. It is set by default to 0.
If you don't use a SkipPolicy and configure it instead with skip(Exception.class) it is very easy to forget setting the additional property skipLimit.
Could you provide a more suitable default value?
My suggestion would be Integer.MAX_VALUE.
What do you think?
The text was updated successfully, but these errors were encountered: