Yes, of course...
I have opened a JIRA [1] and start working on it.
[1] https://issues.apache.org/jira/browse/CAMEL-7700
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Memb
Hi
IMHO you should only set that fetch limit if getMaxMessagesPerPoll >
0. So the user needs to set that option explicit if he/she want to
limit it.
On Wed, Aug 13, 2014 at 2:07 PM, Christian Müller
wrote:
> At present, we do not limit the fetch size on the JDBC driver level which
> will fix t
At present, we do not limit the fetch size on the JDBC driver level which
will fix this issue (e.g.
preparedStatement.setFetchSize(getMaxMessagesPerPoll())).
The drawback is, we don't know how many rows are in the database which will
match our query. We only can assume if fetchSize is equal to
maxM
Add "limit 500" (or whatever) to the end of your query. Unless you're
expecting some sort of streaming ResultSet support sort of thing, but that
might require some workarounds.
On 8 August 2014 17:32, Matt Payne wrote:
> I fixed this at the database level by limiting how many rows can come back
I fixed this at the database level by limiting how many rows can come back
using SQL.
Is there a reason camel does not allow the limiting of how many rows are
pulled from the result set?
Thanks! --Matt Payne
On Fri, Aug 8, 2014 at 3:34 PM, Matt Payne wrote:
> I am getting an java.lang.OutOfM
