spring-batch

问题 Job runs once and try to process all the files available in a source folder in a step. Further it need to do removal of processed/tried but failed files from the source folder to another subsequent folders (/_archived, /_faild). What is the best way to move successfully processed files in archive folder and unsuccessfull files in error folder categorically using spring batch. 回答1: you can add separate tasklet or use JobExecutionListener.afterJob hook to move files. Below is sample example for

问题 I have simple Spring-Service that (among other tasks) starts a spring batch job with the following code: @Autowired private JobRegistry jobRegistry; @Autowired private JobLauncher jobLauncher; public void startMyJob() { Job job = jobRegistry.getJob("myJobName"); JobParameters jobParameters = new JobParametersBuilder().toJobParameters(); jobLauncher.run(job, jobParameters); } This works fine, as long as there is no transaction active when the Serivce-Method is called. However, with an active

问题 I have simple Spring-Service that (among other tasks) starts a spring batch job with the following code: @Autowired private JobRegistry jobRegistry; @Autowired private JobLauncher jobLauncher; public void startMyJob() { Job job = jobRegistry.getJob("myJobName"); JobParameters jobParameters = new JobParametersBuilder().toJobParameters(); jobLauncher.run(job, jobParameters); } This works fine, as long as there is no transaction active when the Serivce-Method is called. However, with an active

问题 I have successfully halted a job from a before step with this method. public class FirstListener implements StepExecutionListener { @Override public void beforeStep(StepExecution stepExecution) { boolean shouldRun = shouldJobRun(); if (!shouldRun) { // listeners will still work, but any other step logic (reader, processor, writer) will not happen stepExecution.setTerminateOnly(); stepExecution.setExitStatus(new ExitStatus("STOPPED", "Job should not be run right now.")); LOGGER.warn(duplicate

问题 According to the Spring Batch documentation restarting of a job is supported out of the box but I cannot get it to start from where it left of. e.g. If my step processed 10 records it should start at record 11 with processing whenever I restart it. In practice this doesn't happen. It reads from the beginnen en reprocesses everything. Does anybody have a Java config based configuration of a simple job that reads a delimited file and writes the content to a db table that can be restarted from

问题 According to the Spring Batch documentation restarting of a job is supported out of the box but I cannot get it to start from where it left of. e.g. If my step processed 10 records it should start at record 11 with processing whenever I restart it. In practice this doesn't happen. It reads from the beginnen en reprocesses everything. Does anybody have a Java config based configuration of a simple job that reads a delimited file and writes the content to a db table that can be restarted from

问题 I am implementing spring batch job for processing millions of records in a DB table using partition approach as follows - Fetch a unique partitioning codes from table in a partitioner and set the same in execution context. Create a chunk step with reader,processor and writer to process records based on particular partition code. Is this approach is proper or is there any better approach for situation like this? As some partition codes can have more number of records than others,so those with

问题 I am implementing spring batch job for processing millions of records in a DB table using partition approach as follows - Fetch a unique partitioning codes from table in a partitioner and set the same in execution context. Create a chunk step with reader,processor and writer to process records based on particular partition code. Is this approach is proper or is there any better approach for situation like this? As some partition codes can have more number of records than others,so those with

问题 I am implementing spring batch job for processing millions of records in a DB table using partition approach as follows - Fetch a unique partitioning codes from table in a partitioner and set the same in execution context. Create a chunk step with reader,processor and writer to process records based on particular partition code. Is this approach is proper or is there any better approach for situation like this? As some partition codes can have more number of records than others,so those with

问题 I am implementing spring batch job for processing millions of records in a DB table using partition approach as follows - Fetch a unique partitioning codes from table in a partitioner and set the same in execution context. Create a chunk step with reader,processor and writer to process records based on particular partition code. Is this approach is proper or is there any better approach for situation like this? As some partition codes can have more number of records than others,so those with