We have a scenario where the commit-interval is being set for each job by the admin. The value is stored in database. How can we set the commit-interval value for the chunk ,dynamically and not by specifying it in the xml (configuration).
Printable View
We have a scenario where the commit-interval is being set for each job by the admin. The value is stored in database. How can we set the commit-interval value for the chunk ,dynamically and not by specifying it in the xml (configuration).
I guess you can refer to job parameters when setting up the commit interval. Try with the usual #{jobParameters['my.key']} syntax and you would be able to specify the commit when launching the job.
You can either use parameters (as noted by @arno) or you could create a custom CompletionPolicy that either reads from that database as you mentioned or accepts the parameters.
The job parameters solution is straightforward but it impacts the identity of the job instance, thus restartability. The dynamic completion policy solution is more difficult to set up, but more elegant I guess.