Bug description
JobRepository#getJobNames() is not implemented by the only implementation of the interface, SimpleJobRepository. The default method simply returns an empty list.
As of Spring Batch 5, this method is used by JobRepositoryTestUtils.removeJobExecutions(), which became a no-op method, never removing any executions due to getJobNames() never returning any job names.
Environment
Spring Batch 5.0.0-RC2
Steps to reproduce
- Run Job.
- Call
JobRepository.getJobNames().
Expected behavior
Names of jobs are returned.
Minimal Complete Reproducible example
demo1.zip
- Unzip
- Run
mvnw spring-boot:run
- The app runs a job named
job and then queries both the batch_job_instance table and the JobRepository for all job names. The query returns job as expected, the JobRepository returns nothing.
Bug description
JobRepository#getJobNames()is not implemented by the only implementation of the interface,SimpleJobRepository. The default method simply returns an empty list.As of Spring Batch 5, this method is used by
JobRepositoryTestUtils.removeJobExecutions(), which became a no-op method, never removing any executions due togetJobNames()never returning any job names.Environment
Spring Batch 5.0.0-RC2
Steps to reproduce
JobRepository.getJobNames().Expected behavior
Names of jobs are returned.
Minimal Complete Reproducible example
demo1.zip
mvnw spring-boot:runjoband then queries both thebatch_job_instancetable and theJobRepositoryfor all job names. The query returnsjobas expected, theJobRepositoryreturns nothing.