Issue Details (XML | Word | Printable)

Key: BATCH-221
Type: Sub-task Sub-task
Status: Closed Closed
Resolution: Won't Fix
Priority: Minor Minor
Assignee: Lucas Ward
Reporter: Dave Syer
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Spring Batch
BATCH-220

Remove Skippable from existing implementations.

Created: 29/Nov/07 07:29 AM   Updated: 19/Jun/08 02:29 AM
Component/s: Core, Infrastructure
Affects Version/s: 1.0-m3
Fix Version/s: 1.1.0
Security Level: Public (Public Issues)

Time Tracking:
Original Estimate: 0.5d
Original Estimate - 0.5d
Remaining Estimate: 0.5d
Remaining Estimate - 0.5d
Time Spent: Not Specified
Remaining Estimate - 0.5d


 Description  « Hide
Remove Skippable from existing implementations. It won't be needed if there is a chunk-oriented approach to processing.

 All   Comments   Work Log   Change History   FishEye   Builds      Sort Order: Ascending order - Click to sort in descending order
Ben Hale added a comment - 20/Mar/08 05:53 AM
Lucas,
  This is sorted right? Already completed with the ItemStream stuff?

Lucas Ward added a comment - 20/Mar/08 10:28 AM
Actually no, this is more like a 'won't fix'. the issue came around when we were going to switch to chunked processing. We didn't need the readers to know that an Item should be skipped. However, with read and write in the same transaction they have to know, so that in a rollback scenario they don't give us back the skipped items again.