Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C12FCF775 for ; Mon, 8 Apr 2013 19:35:14 +0000 (UTC) Received: (qmail 66920 invoked by uid 500); 8 Apr 2013 19:35:14 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 66833 invoked by uid 500); 8 Apr 2013 19:35:14 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 66825 invoked by uid 99); 8 Apr 2013 19:35:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Apr 2013 19:35:14 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of christian.mueller@gmail.com designates 209.85.219.44 as permitted sender) Received: from [209.85.219.44] (HELO mail-oa0-f44.google.com) (209.85.219.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Apr 2013 19:35:08 +0000 Received: by mail-oa0-f44.google.com with SMTP id h1so6633534oag.17 for ; Mon, 08 Apr 2013 12:34:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=fbrsDYbzR1ubGdMLRtXVd/e2PxPyEOtDtxPyxangYwg=; b=y9wQGsMiH+j7ZH8BHjysGGrdUU0fxVZ+kJipfyoKtRIBqSdjc2w9eMnMjObEaQvW2K yjeeqBqV03xqOpmtUzgWf6KoREe02vYad20PNFzQG4XrrvwAa0Y9hNDg1RX3p90DZavV cLUD1iCRbMlFZ2m4PnjoxkP7/twbvRSS+RLoZVbYiiWrpvdMNRthhDhqEJEoeGeeDwsF yE07LSnGxx/WhDVPm/2GpBv14JBXrXDNxyyHbJy7E025nMiutO2ROqpVesmUKbGotzRF 9m3OCdjufiCQywpqORcFO0VYWFtv0AXWV5UtaTmH+7yBSw89KY/UoCXPloJ/xYP2rZ56 dxFQ== MIME-Version: 1.0 X-Received: by 10.60.171.50 with SMTP id ar18mr16091163oec.24.1365449687208; Mon, 08 Apr 2013 12:34:47 -0700 (PDT) Received: by 10.182.132.168 with HTTP; Mon, 8 Apr 2013 12:34:47 -0700 (PDT) Received: by 10.182.132.168 with HTTP; Mon, 8 Apr 2013 12:34:47 -0700 (PDT) In-Reply-To: <1365431251710-5730509.post@n5.nabble.com> References: <1365431251710-5730509.post@n5.nabble.com> Date: Mon, 8 Apr 2013 21:34:47 +0200 Message-ID: Subject: Re: JDBC component handling large results From: =?ISO-8859-1?Q?Christian_M=FCller?= To: dev@camel.apache.org Content-Type: multipart/alternative; boundary=bcaec550af3a909a6e04d9de87f0 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec550af3a909a6e04d9de87f0 Content-Type: text/plain; charset=ISO-8859-1 You can limit the returned row count in your query. Does this work for you? Sent from a mobile device Am 08.04.2013 16:35 schrieb "yazan" : > 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 the rows returned from a query are processed. The JDBC component only > create a producer that executes a sql statement it received in a body of > an > exchange. My question is about the best approach to do this "1 exchange" to > a "series of exchanges" mapping, My research lead me to MulticastProcessor > it seems that I should make JDBCProducer extend it and then override > createProcessorExchangePairs to create an Iterable > that actually reads rows from the resultset to populate each new exchange, > Am I on the right track here? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/JDBC-component-handling-large-results-tp5730509.html > Sent from the Camel Development mailing list archive at Nabble.com. > --bcaec550af3a909a6e04d9de87f0--