spring-projects / spring-projects/spring-batch
Make 'Exception mode' transparent in Listeners [BATCH-2338]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 2.5k
- Avg merge
- 6d 53m
- Merged PRs (30d)
- 3
Description
Wolfgang Grossinger opened BATCH-2338 and commented
As discussed in BATCH-2334, some items may be reprocessed after an Exception, what results that some listener methods are executed twice. This can be a problem in some circumstances: for example, I use an ItemWriteListener to count processed/errorneous items which results in wrong statistics if some items are counted twice. For me, this is a bad thing but I can cope with it. But there might be more serious issues that may be harder to circumvent.
So what I would really appreciate is some kind of possibility to detect, if I am in 'exception mode', so that I can act according to the current situation.
No further details from BATCH-2338
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
Start by tracing the ItemWriteListener callbacks and the exception/reprocessing behavior described in the issue. No files, tests, entry points, or completion criteria are named, so the expected observable way to detect exception mode must be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100