There is a suggested workaround in
https://apacheignite-sql.readme.io/docs/performance-and-debugging#section-sql-performance-and-usability-considerations,
item 2
As a workaround...you can rewrite the query in the following way: select
p.name from Person p join table(id bigint = ?) i on p.id = i.i
Has it been fixed in 2.4 ?
Looks like it is not, when I generate the explain plan for a query which has
a composite key
Here are the queries I ran and explain plan results.
When I use IN, it uses the full table scan, otherwise It does look up on
primary key
explain SELECT * FROM "MapLonglistCach
It looks like an issue in H2 database engine, but it was fixed in newest
versions.
In Ignite-1.7.0 (which is on the vote right now) we upgraded H2, so it must
be ok.
Sergi
2016-08-04 11:19 GMT+03:00 Zhengqingzheng :
> Hi there,
>
> When we using ignite sql query, we find that IN clause cannot u
