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: <1486952770430-10582.post@n6.nabble.com>
References: <CANCAXEEZZ7fYcOJSfNvXcrb_ZvihkB2=eE+p03hm=5_R+qppaw@mail.gmail.com>
 <CALPm_-CHLeMS4Cdd+nfjK2j316Ayf1MgUdZpQMvsHJ+yfPi0Fw@mail.gmail.com>
 <1486503973077-10492.post@n6.nabble.com> <CALPm_-DEMR+msL=KmkfW105n46Y-oudM546SWV_-U8wZd3VAjw@mail.gmail.com>
 <1486590496794-10506.post@n6.nabble.com> <CALPm_-BZUM6=eQMVWV8GfVcTKxoHtWdjbTDcO8pCK9sweKtVKg@mail.gmail.com>
 <CALPm_-DTUcaEb4NCzrGROTYgJKb-Jx3vW3wUCdsRTVz7H3Kmig@mail.gmail.com>
 <CALPm_-Duj37FbecuAO1uLSVKgzwSYuS6_yzADYk3Pnr+aVNyQA@mail.gmail.com>
 <CANCAXEE5sFBO5mkK7An_aj0FA8F=vJdDuz4ZSME4EzpJCUhYcw@mail.gmail.com>
 <CALPm_-Ad9CjqDZrMUa-6KhaTiYcmyLw8H_jMo2ju-XaeO3iiZQ@mail.gmail.com> <1486952770430-10582.post@n6.nabble.com>
From: Anil <anilklce@gmail.com>
Date: Mon, 13 Feb 2017 09:29:01 +0530
Message-ID: <CALPm_-A5z2kXRvHD6UVXxPBSKoSz9j7+iz=pVB23xyhXRHRoeQ@mail.gmail.com>
Subject: Re: NOT IN in ignite
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a11402fc026a2c60548617a9d
archived-at: Mon, 13 Feb 2017 03:59:52 -0000

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

Hi Val,

When two cache's require a join, collocation must be true in jdbc
connection and then group by queries on individual caches will not return
aggregated results.  you mean this is not limitation ? if Yes, i am sorry,
i may not agree on this :(

in this case, to make sql queries work, two jdbc client must be created..
one for queries of individual cache and other for join queries.

Thanks


On 13 February 2017 at 07:56, vkulichenko <valentin.kulichenko@gmail.com>
wrote:

> Anil,
>
> I don't see any limitations (except IGNITE-3860). Aggregation without
> collocation works properly and return correct result unless collected flag
> is set to true (doing so in this scenario is a misuse). As for performance,
> collocated execution will always be faster than non-collocated. That's true
> for any distributed system and there is no magic, you know :)
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/NOT-IN-in-ignite-tp9861p10582.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

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

<div dir=3D"ltr"><div>Hi Val,</div><div><br></div><div>When two cache&#39;s=
 require a join, collocation must be true in jdbc connection and then group=
 by queries on individual caches will not return aggregated results. =C2=A0=
you mean this is not limitation ? if Yes, i am sorry, i may not agree on th=
is :(</div><div><br></div><div>in this case, to make sql queries work, two =
jdbc client must be created.. one for queries of individual cache and other=
 for join queries.=C2=A0</div><div><br></div><div>Thanks</div><div><br></di=
v><div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On 13 February 2017 at 07:56, vkulichenko <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:valentin.kulichenko@gmail.com" target=3D"_blank">valentin.kuli=
chenko@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">An=
il,<br>
<br>
I don&#39;t see any limitations (except IGNITE-3860). Aggregation without<b=
r>
collocation works properly and return correct result unless collected flag<=
br>
is set to true (doing so in this scenario is a misuse). As for performance,=
<br>
collocated execution will always be faster than non-collocated. That&#39;s =
true<br>
for any distributed system and there is no magic, you know :)<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/NOT-IN-in-ignite-tp9861p10582.html" rel=3D"noreferrer" target=
=3D"_blank">http://apache-ignite-users.<wbr>70518.x6.nabble.com/NOT-IN-in-<=
wbr>ignite-tp9861p10582.html</a><br>
Sent from the Apache Ignite Users mailing list archive at Nabble.com.<br>
</blockquote></div><br></div>

--001a11402fc026a2c60548617a9d--