spring-projects / spring-projects/spring-batch
Add optimization for commit-interval=1 [BATCH-1518]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 2.5k
- Avg merge
- 6d 53m
- Merged PRs (30d)
- 3
Description
Dave Syer opened BATCH-1518 and commented
If there is only one item in the chunk then there is no need to scan it for failures on a write error
This issue is a sub-task of BATCH-1511
Referenced from: commits https://github.com/spring-projects/spring-batch/commit/17daf7ab0790b779db8c28d2906d9f83c7290ad3, https://github.com/spring-projects/spring-batch/commit/561db8ddb88eacdbba53d60dd60a6c7d55479848, https://github.com/spring-projects/spring-batch/commit/b6aca5fa05fff81a34d4e24f3faa3e4576249e45, https://github.com/spring-projects/spring-batch/commit/01697d9ffaa21f2ec6239954dafc3aa3b02c9d3a
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the four referenced commits and the parent BATCH-1511 context first. Trace the single-item chunk path for a write error and confirm that commit-interval=1 avoids scanning for failures while preserving the expected failure behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100