spring-projects / spring-projects/spring-batch
Documentation: provide a minimal working example of a setup using an embedded job repository and a physical DB for item readers/writers
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 2.5k
- Avg merge
- 6d 53m
- Merged PRs (30d)
- 3
Description
After the removal of the in-memory job repository (I know, it was not for production use) I think that using two datasources will become a very common use case (for example H2 for the job repo and Oracle for business operations). Having a minimal working example of such setup would simplify migrations.
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 reviewing Spring Batch's configuration entry points for the job repository, data sources, and item readers and writers. Then inspect the repository's existing documentation or examples for a suitable location. Done means a minimal working example demonstrates an embedded job repository using one data source and item operations using a separate physical database data source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, databases, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100