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: <1712435395.669561.1464956586077.JavaMail.yahoo@mail.yahoo.com>
References: <1712435395.669561.1464956586077.JavaMail.yahoo.ref@mail.yahoo.com>
 <1712435395.669561.1464956586077.JavaMail.yahoo@mail.yahoo.com>
From: Alexey Goncharuk <alexey.goncharuk@gmail.com>
Date: Fri, 3 Jun 2016 09:36:32 -0700
Message-ID: <CABDss3ixJRSbcGpR+iPK2R2S-KgncPMyWCSEd-bxsAZ5Br0NVQ@mail.gmail.com>
Subject: Re: Ignite - Question about update counter field for continuous queries
To: user@ignite.apache.org, M Singh <mans2singh@yahoo.com>
Content-Type: multipart/alternative; boundary=001a1145a35a5937e10534625313
archived-at: Fri, 03 Jun 2016 16:36:48 -0000

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

Hi,

Ignite client automatically checks the partition counter and filters out
duplicate events, you do not need to do it manually to get rid of
duplicates. However, starting from Ignite 1.6 update counter is available
through CacheQueryEvent API.

2016-06-03 5:23 GMT-07:00 M Singh <mans2singh@yahoo.com>:

> Hi Folks:
>
> I have a question about once only event delivery for continuous queries.
>
> The document (https://apacheignite.readme.io/docs/continuous-queries)
> indicates that there is a per partition update counter which is sent to the
> client along with the change notification.  I checked the CacheEntryEvent
> and could not find the update counter field.  Also, is this field (update
> counter) handled internally by Ignite client library (dropping duplicate
> events on the client side) or does the client listener has to check it in
> case of duplicate events.  If the client listener has to check the update
> counter, please let me know how to access this field.
>
> Thanks
>
> Mans
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>Ignite client automatically checks =
the partition counter and filters out duplicate events, you do not need to =
do it manually to get rid of duplicates. However, starting from Ignite 1.6 =
update counter is available through CacheQueryEvent API.</div></div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">2016-06-03 5:23 GMT-07:0=
0 M Singh <span dir=3D"ltr">&lt;<a href=3D"mailto:mans2singh@yahoo.com" tar=
get=3D"_blank">mans2singh@yahoo.com</a>&gt;</span>:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><div><div style=3D"color:#000;background-color:#fff;font-family:=
HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-=
size:16px"><div>Hi Folks:</div><div><br></div><div dir=3D"ltr">I have a que=
stion about once only event delivery for continuous queries. =C2=A0</div><d=
iv dir=3D"ltr"><br></div><div dir=3D"ltr">The document (<a href=3D"https://=
apacheignite.readme.io/docs/continuous-queries" target=3D"_blank">https://a=
pacheignite.readme.io/docs/continuous-queries</a>) indicates that there is =
a per partition update counter which is sent to the client along with the c=
hange notification.=C2=A0 I checked the CacheEntryEvent and could not find =
the update counter field.=C2=A0 Also, is this field (update counter) handle=
d internally by Ignite client library (dropping duplicate events on the cli=
ent side) or does the client listener has to check it in case of duplicate =
events.=C2=A0 If the client listener has to check the update counter, pleas=
e let me know how to access this field.</div><div dir=3D"ltr"><br>Thanks</d=
iv><div dir=3D"ltr"><br>Mans</div>


</div></div></blockquote></div><br></div>

--001a1145a35a5937e10534625313--