Skip to content

Conversation

isanghaessi
Copy link
Contributor

@isanghaessi isanghaessi commented Aug 15, 2025

Summary

This PR fixes #4755 .
Problem is, job with having zero identifier job parameters are able to restart.
Job what having COMPLETED status should not be able to restart with same Job Parameters.

Changes

  • Removed exception condition for job parameters with no identifier job parameters.
  • Add test case.
  • Edit test cases made assuming empty identifying job parmaeters can be restarted.

…ob parameters

commit 57498c7
Author: Seungyong Hong <[email protected]>
Date:   Sat Aug 16 15:37:35 2025 +0900

    Fix wrong behavior of JobRepository with empty identifying job parameters

    - Update test casese.

    Signed-off-by: Seungyong Hong <[email protected]>

commit 4d5a3d6
Author: Seungyong Hong <[email protected]>
Date:   Sat Aug 16 14:44:25 2025 +0900

    Fix wrong behavior of JobRepository with empty identifying job parameters

    - formatting.

    Signed-off-by: Seungyong Hong <[email protected]>

commit 0ce9de6
Author: Seungyong Hong <[email protected]>
Date:   Fri Aug 15 23:04:26 2025 +0900

    Fix wrong behavior of JobRepository with empty identifying job parameters

    - simplify brackets.

    Signed-off-by: Seungyong Hong <[email protected]>

commit 45efc57
Author: Seungyong Hong <[email protected]>
Date:   Fri Aug 15 20:43:39 2025 +0900

    Fix wrong behavior of JobRepository with empty identifying job parameters

    - Job has to be not completed whether empty identifying job parameters or not.

    Signed-off-by: Seungyong Hong <[email protected]>

Signed-off-by: Seungyong Hong <[email protected]>
@isanghaessi isanghaessi changed the title Gh 4755: Fix wrong behavior of JobRepository with empty identifying job parameters GH-4755: Fix wrong behavior of JobRepository with empty identifying job parameters Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Spring batch allows job without parameters to restart even if the job already completed successfully
1 participant