Java Reference
In-Depth Information
Table 2-6.
BATCH_STEP_EXECUTION Table
•
Field
•
Description
•
Value
STEP_EXECUTION_ID
Primary key for the table
1
VERSION
The version of the record
2
STEP_NAME
The name of the step as it's configured in the
job's XML
step1
JOB_EXECUTION_ID
Foreign key back to the
BATCH_JOB_EXECUTION table
1
START_TIME
The time the step was started
2010-10-25 18:08:30
END_TIME
The time the step completed, regardless of
result
2010-10-25 18:08:30
STATUS
The current status of the step
COMPLETED
COMMIT_COUNT
The commit count the step is currently on
1
READ_COUNT
The read count the step is currently on
0
FILTER_COUNT
The number of items that have been filtered
0
WRITE_COUNT
The number of items that have been written
0
READ_SKIP_COUNT
The number of items that have been skipped
being read
0
WRITE_SKIP_COUNT
The number of items that have been skipped
being written
0
PROCESS_SKIP_COUNT
The number of items that haven't gone
through the ItemProcessor (straight from
ItemReader to ItemWriter)
0
ROLLBACK_COUNT
The total number of rollbacks during the
execution, including each rollback for a given
item skip or retry
0
EXIT_CODE
The exit code that was returned a the step
completed
COMPLETE
EXIT_MESSAGE
Any message returned by the step
LAST_UPDATED
The last time the record was updated
2010-10-25 18:08:30
Job and Step Execution Context Tables
That leaves the two context tables, BATCH_JOB_EXECUTION_CONTEXT and
BATCH_STEP_EXECUTION_CONTEXT. These tables are the persisted versions of the ExecutionContext
related to either the job or the step. The ExecutionContext is the Spring Batch similar to the servlet
context or session in a web application in that it's a global place to store information. It's essentially a
map of key/value pairs that are scoped to either the job or the step. The job or step execution context is
used to pass information around within the given scope; for jobs, it's used to pass information from step
to step, and for steps, it's used to pass information across the processing of multiple records.
The tables BATCH_JOB_EXECUTION_CONTEXT and BATCH_STEP_EXECUTION_CONTEXT are the
serialized version of these maps. In this case, they both contain the same data, with only the foreign key
(which is the primary key of the table) being different (BATCH_STEP_EXECUTION_CONTEXT refers to
