Of course, but I was hoping I can add support for something similar to spring
batch JDBCurserItemReader or JDBCPagingItemReader where the framework
handles most of the details of reading a large result.
--
View this message in context:
http://camel.465427.n5.nabble.com/JDBC-component-handling-l
The JDBC component currently reads all the rows returned by a query in one
shot, this only works for small resultsets. I'm trying to modify the
component to support cursor semantics, so it reads only X numbers of rows,
sets the rows in a new exchange's body and forwards it, rinse repeat until
all t
