spring-projects / spring-projects/spring-batch
Add support to validate job repository configuration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 2.5k
- Avg merge
- 6d 53m
- Merged PRs (30d)
- 3
Description
As of v5.2, it is assumed that the job repository is correctly configured and there is no pre-validation that everything is setup correctly before running a job. Therefore, any mis-configuration of the job repository results in SQL exceptions or NPE like this or #4811 .
The goal of this issue to explore the best way/place to check the configuration of the chosen job repository upfront and fail fast with an informative BatchConfigurationException rather than an SQL exception or a NPE.
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 how the chosen job repository is configured and initialized before a job runs. Compare the current SQL and null-pointer failure paths with the linked issue and define where an informative BatchConfigurationException should be raised; done means invalid repository configuration fails fast with that exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100