May 14th, 2009, 03:41 AM
isolationLevelForCreate = "ISOLATION_SERIALIZABLE";
I got some error messages in oracle when i ran some jobs in parallel. (ORA-08177:can't serialize access for this transaction)
Because isolation level for create is "serializable" as you know.
I wanna know why you've let isolation level Serializable. Is there any policy or something to let this serializable?
Spring Batch 1.1.4
Spring Batch 2.0.0
ItemWriter#write(List<? extends T> items)
I wanna know why SpringBatch 2.0.0 doesn't support ItemWriter#write(Object obj). There are too many problems with the change of 'write' method.
May 14th, 2009, 06:20 AM
#2: it actually solves a lot of problems for most people. It is much more natural to write a list of items, since it allows you to control the performance optimisations like flushing and batch updates in a single method. What is the issue you are encountering?