Ok, thanks.
Moved the discussion here:
http://apache-ignite-developers.2346864.n4.nabble.com/Continuous-queries-and-duplicates-td39444.html
wt., 11 gru 2018 o 14:05 Ilya Kasnacheev
napisał(a):
> Hello!
>
> You could write this message to developers list in a separate th
Hello!
You could write this message to developers list in a separate thread, see
if there will be any discussion.
Regards,
--
Ilya Kasnacheev
ср, 5 дек. 2018 г. в 18:29, piotr.romanski :
> Hi all, I think that Krzysztof raised a valid concern. Actually, in my
> opinion the manual
Hi all, I think that Krzysztof raised a valid concern. Actually, in my
opinion the manual deduplication in some use cases may lead to possible
memory problems on the client side. In order to remove duplicated
notifications which we are receiving in the local listener, we need to keep
all initial
o:ilya.kasnach...@gmail.com]
> Sent: 30 listopada 2018 14:02
> To: user@ignite.apache.org
> Subject: Re: Continuous queries and duplicates
>
> Hello!
>
> There should be isolation in AI 2.7 as an experimental feature.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
.). Are there any plans to enable
isolation on SqlQuery?
-KS
From: Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
Sent: 26 listopada 2018 08:01
To: user@ignite.apache.org
Subject: Re: Continuous queries and duplicates
Hello!
SQL queries have no isolation currently so it is not possible to avoid
cient (can’t use indexes etc.). Are there any plans to
> enable isolation on SqlQuery?
>
> -KS
>
>
>
> *From:* Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
> *Sent:* 26 listopada 2018 08:01
> *To:* user@ignite.apache.org
> *Subject:* Re: Continuous queries and dup
Subject: Re: Continuous queries and duplicates
Hello!
SQL queries have no isolation currently so it is not possible to avoid the
problem that you described. You could try switching to ScanQuery, see if it
helps; or learning to deal with duplicates.
Regards,
--
Ilya Kasnacheev
пт, 23 нояб. 2018
Hello!
SQL queries have no isolation currently so it is not possible to avoid the
problem that you described. You could try switching to ScanQuery, see if it
helps; or learning to deal with duplicates.
Regards,
--
Ilya Kasnacheev
пт, 23 нояб. 2018 г. в 19:25, Sobolewski, Krzysztof <
Hi,
I'm wanting to use a ContinuousQuery and there is a slight issue with how it
transitions from the initial query to the notifications phase. It turns out
that if there are additions to the cache happening while the continuous query
runs, an entry may be reported twice - once by the initial
