Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <1480700876885-9373.post@n6.nabble.com>
References: <CALPm_-A-iED8MnsdtW9JPwikkBqnCipY2SdPexRrFmZcJN1Jww@mail.gmail.com>
 <1480444341175-9272.post@n6.nabble.com> <CALPm_-B5XmGFn8PCv7XQ4ZKZD7ibR3DGu9kwHYnufumBSwmNiQ@mail.gmail.com>
 <1480547090683-9313.post@n6.nabble.com> <CALPm_-Cc=icrpaUy9KCH2BpKUh-8BQEHrXz9PR=6m2=JONxFuQ@mail.gmail.com>
 <1480632087349-9342.post@n6.nabble.com> <CALPm_-Ao=5Ev3sko63TMD_1M7pq9mPOhnz=TeqQ1pD0fEg08bw@mail.gmail.com>
 <1480700876885-9373.post@n6.nabble.com>
From: Anil <anilklce@gmail.com>
Date: Sat, 3 Dec 2016 08:49:19 +0530
Message-ID: <CALPm_-Cjfvy84tCtp=7r3ayomJfo7vWk44y1LfP1xnXKqt7qUQ@mail.gmail.com>
Subject: Re: Fetching large number of records
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a11474ba494d5b40542b887ae
archived-at: Sat, 03 Dec 2016 03:20:04 -0000

--001a11474ba494d5b40542b887ae
Content-Type: text/plain; charset=UTF-8

Hi Val,

Thanks for clarification. I understand something and i will give a try.

Thanks.

On 2 December 2016 at 23:17, vkulichenko <valentin.kulichenko@gmail.com>
wrote:

> Anil,
>
> The JdbcQueryTask is executed each time the next page is needed. And the
> number of rows returned by the task is limited by fetchSize:
>
>     if (rows.size() == fetchSize) // If fetchSize is 0 then unlimited
>         break;
>
> The cursor is cached and reused there, so is this task is executed twice
> for
> the same result set, it will not execute the query from scratch, but will
> get the existing cursor and start iteration from where it finished on the
> first invocation.
>
> I'm not completely sure that I correctly understand what you mean by
> streaming here, but paging is definitely in place and that's how it works
> now.
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Fetching-large-number-of-records-tp9267p9373.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

--001a11474ba494d5b40542b887ae
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Val,<div><br></div><div>Thanks for clarification. I und=
erstand something and i will give a try.</div><div><br></div><div>Thanks.</=
div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 2 De=
cember 2016 at 23:17, vkulichenko <span dir=3D"ltr">&lt;<a href=3D"mailto:v=
alentin.kulichenko@gmail.com" target=3D"_blank">valentin.kulichenko@gmail.c=
om</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Anil,<br>
<br>
The JdbcQueryTask is executed each time the next page is needed. And the<br=
>
number of rows returned by the task is limited by fetchSize:<br>
<br>
=C2=A0 =C2=A0 if (rows.size() =3D=3D fetchSize) // If fetchSize is 0 then u=
nlimited<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 break;<br>
<br>
The cursor is cached and reused there, so is this task is executed twice fo=
r<br>
the same result set, it will not execute the query from scratch, but will<b=
r>
get the existing cursor and start iteration from where it finished on the<b=
r>
first invocation.<br>
<br>
I&#39;m not completely sure that I correctly understand what you mean by<br=
>
streaming here, but paging is definitely in place and that&#39;s how it wor=
ks<br>
now.<br>
<br>
-Val<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-ignite-users.70518.x=
6.nabble.com/Fetching-large-number-of-records-tp9267p9373.html" rel=3D"nore=
ferrer" target=3D"_blank">http://apache-ignite-users.<wbr>70518.x6.nabble.c=
om/Fetching-<wbr>large-number-of-records-<wbr>tp9267p9373.html</a><br>
Sent from the Apache Ignite Users mailing list archive at Nabble.com.<br>
</blockquote></div><br></div>

--001a11474ba494d5b40542b887ae--