You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Nikolai Tikhonov <nt...@apache.org> on 2017/05/01 09:40:30 UTC
Re: Distributed Closures VS Executor Service
Hi,
The page [1] contains also workaround for IN operation. You can use JOIN
instead of IN.
Sergi,
Will this tip actual for 2.0 version yet?
1. https://apacheignite.readme.io/docs/sql-performance-and-
debugging#sql-performance-and-usability-considerations
On Sun, Apr 30, 2017 at 1:50 PM, kmandalas <
Kyriakos.Mandalas@iriworldwide.com> wrote:
> After investigation more I run into the following:
>
> https://apacheignite.readme.io/docs/sql-performance-and-
> debugging#sql-performance-and-usability-considerations
>
> So, cause my query has IN clause no indexing will be used anyway.
>
> Could you please elaborate more on this topic and if/what will change at
> version 2.0? Should I open a different topic better?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-
> tp11192p12314.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Distributed Closures VS Executor Service
Posted by kmandalas <Ky...@IRIworldwide.com>.
Dear all,
I have created a new Topic: "Ignite SQL Indexing Performance problems" since
the conversation has deviate a lot form the original subject.
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p12347.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Distributed Closures VS Executor Service
Posted by kmandalas <Ky...@IRIworldwide.com>.
Hello,
I don't know about H2, I sent you link from apacheignite.readme.io which
describes that IN clause does not support Indexes when run on Ignite. Also
at my previous post I have sent a simply query using IN clause that has very
poor performance on Ignite even run only on local mode with less than 2
million entries.
So could you please provide a concrete feedback?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p12335.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Distributed Closures VS Executor Service
Posted by Sergi Vladykin <se...@gmail.com>.
Actually H2 can use index for IN operator, but using JOIN instead of IN may
be still useful.
Sergi
2017-05-01 12:40 GMT+03:00 Nikolai Tikhonov <nt...@apache.org>:
> Hi,
>
> The page [1] contains also workaround for IN operation. You can use JOIN
> instead of IN.
>
> Sergi,
>
> Will this tip actual for 2.0 version yet?
>
> 1. https://apacheignite.readme.io/docs/sql-performance-and-debugging#sql-
> performance-and-usability-considerations
>
> On Sun, Apr 30, 2017 at 1:50 PM, kmandalas <Kyriakos.Mandalas@
> iriworldwide.com> wrote:
>
>> After investigation more I run into the following:
>>
>> https://apacheignite.readme.io/docs/sql-performance-and-debu
>> gging#sql-performance-and-usability-considerations
>>
>> So, cause my query has IN clause no indexing will be used anyway.
>>
>> Could you please elaborate more on this topic and if/what will change at
>> version 2.0? Should I open a different topic better?
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Distributed-Closures-VS-Executor-Service-t
>> p11192p12314.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>