Hi Shravya!
It caused by bug in H2 parser which erases information about type of the column
expression of subqueries and reports it just like ‘column’, so Ignite can’t
properly split the query.
For thin client the splitting is not always needed since the requests starts
its execution on the
Hi,
For Ignite thick client, the below sql query is throwing CacheException with
the following code:
public class ClientNode {
public static void main(String[] args) {
IgniteConfiguration igniteCfg = new IgniteConfiguration();
igniteCfg.setClientMode(true);
Ignite
