Why Spring batch allows job without parameters to restart even if the job already completed successfullly? #4694
Unanswered
ELMORABITYounes
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Right now even if a job was completed successfuly, spring batch allow It to be restarted if It contains no identifying params as shown here:
I am wondering why is that done like this? I mean if the job already completed why It does not throw JobInstanceAlreadyCompleteException? Shouldn't second job instance without param considered the same and hence not allow It to be restarted if already succeeded?
Beta Was this translation helpful? Give feedback.
All reactions