I have been working with Spring Batch framework for a while now. As much as I have found it comfortable to work with, there are instances when I get confounded by some interesting batch specific idea.
For instance, when you use chunking for data processing, it is a common thing to use a reader, processor and writer for processing the data chunks.
Note here that the chunk size is not 1 unless it has been explicitly specified so in the batch description xml.
Remember that exclusivity of private data in the chunk processing pipeline is only between items of different chunks and not between items of the same chunk.
For example:
class MockProcessor implements ItemProcessor <K,V> {
private Map <K,V> cache;
public void Process () {
//use cache
cache.put (k,v);
}
}
Here, the cache contents are private and exclusive only for items belonging to different chunks and not for items in the same chunk. So, if you have any item specific processing to do, remember to set the chunk size to 1 or a better idea would be clear and initialize your cache upon each process invocation.
For example:
class MockProcessor implements ItemProcessor <K,V> {
private Map <K,V> cache;
public void Process () {
//use cache
cache.put (k,v);
}
}
Here, the cache contents are private and exclusive only for items belonging to different chunks and not for items in the same chunk. So, if you have any item specific processing to do, remember to set the chunk size to 1 or a better idea would be clear and initialize your cache upon each process invocation.
No comments:
Post a Comment