You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
Between version 4.3.8 and 4.3.9, an increase in the number of requests on table BATCH_JOB_EXECUTION_PARAMS is observed. With each new batch execution, there is one an additional request.
Environment
Java 17
spring-boot-starter-parent 2.7.17
postgresql
spring-batch-core 4.3.9 (or 4.3.8 to show the difference)
Steps to reproduce
Run the same batch with allowStartIfComplete=true several times.
The number of SELECT is increasing by one each time. spring-batch-demo.zip
Expected behavior
The number of SELECT should not be dependent on the number of previous executions.
With large history on table BATCH_JOB_EXECUTION_PARAMS, the number of SELECT is equally important. Considering this table has no index, there is a performance issue.
The text was updated successfully, but these errors were encountered:
arno750
changed the title
Number of request to BATCH_JOB_EXECUTION_PARAMS depending on the number of previous execution
Number of requests to BATCH_JOB_EXECUTION_PARAMS depending on the number of previous executions
Nov 25, 2023
Bug description
Between version 4.3.8 and 4.3.9, an increase in the number of requests on table BATCH_JOB_EXECUTION_PARAMS is observed. With each new batch execution, there is one an additional request.
Environment
Steps to reproduce
Run the same batch with allowStartIfComplete=true several times.
The number of SELECT is increasing by one each time.
spring-batch-demo.zip
Expected behavior
The number of SELECT should not be dependent on the number of previous executions.
With large history on table BATCH_JOB_EXECUTION_PARAMS, the number of SELECT is equally important. Considering this table has no index, there is a performance issue.
The text was updated successfully, but these errors were encountered: