Bug 4529 - Confusing description for checkpointing
Confusing description for checkpointing
Status: RESOLVED FIXED
Product: jbatch
Classification: Unclassified
Component: source
1
All All
: P5 normal
: ---
Assigned To: cvignola
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-17 15:26 UTC by mminella
Modified: 2013-01-24 01:46 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mminella 2013-01-17 15:26:56 UTC
In section 5.2.1 on page 17, the verbiage is confusing.  It sounds like checkpointing occurs throughout a chunk instead of defining the beginning and ending of a chunk.
Comment 1 waynexlund 2013-01-23 19:42:18 UTC
I think the confusing sentence is "A chunk may be configured so the batch runtime periodically checkpoints the progress of the step by committing the current transaction and starting a new transaction scope."  I think adding the text "The default is that transaction boundary is aligned with the item-count, meaning that the transaction is demarcated at the beginning and ending of the chunk boundary".
Comment 2 cvignola 2013-01-23 20:58:54 UTC
Point taken.

I reworded from this:

A chunk runs in the scope of a transaction.  A chunk may be configured so the batch runtime periodically checkpoints the progress of the step by committing the current transaction and starting a new transaction scope.

to this: 


A chunk type step is periodically checkpointed by the batch runtime according to a configured checkpoint policy. Items processed between checkpoints are referred to as a "chunk". Each chunk is processed in a separate transaction. See section 6.7 for more details on transactionality.
Comment 3 waynexlund 2013-01-24 01:46:10 UTC
I'm good with the change.