How could using the split pattern avoid memory overload?

Hi I always to do work , it seems the split pattern could resolve, but will encounter memory overload problem. To illustrate the problem, lets' take a example: Often , we need to query records from a database , but the records matched the condition are too much , and cannot load

Re: How could using the split pattern avoid memory overload?

Does the split-pattern support the bean-express to return a Enumeration instead of List? Hi I always to do work , it seems the split pattern could resolve, but will encounter memory overload problem. To

Re: How could using the split pattern avoid memory overload?

Oh, I am stupid; The camel's document said clearly, the bean return iterator, and using stream model could resolve my problem; --- Does the split-pattern support the bean-express to return a Enumeration instead of List?