Hi Anil, I should although mention that Replicated caches can participate in same query with partitioned caches regardless a degree of parallelizm. This limitation relates to partitioned caches only.
On Mon, Mar 20, 2017 at 3:54 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Hi Anil, > > It is ok. Doc says *"If a query contains JOINs, then all the > participating caches must have the same degree of parallelism.".* > Possibly, it is easy to fix but there can be unobvious limitations, so we > need a time to make a POC. > I believe, it will be fixed in future releases. > > On Mon, Mar 20, 2017 at 1:11 PM, Anil <anilk...@gmail.com> wrote: > >> Hi Andrey, >> >> I see few more issues with IGNITE-4826 >> >> 1. queryParallelism should be used for all caches for which queries are >> used other it throws following exception. >> >> Caused by: java.sql.SQLException: Failed to query Ignite. >> at org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery( >> JdbcStatement.java:131) >> at org.apache.ignite.internal.jdbc2.JdbcPreparedStatement.execu >> teQuery(JdbcPreparedStatement.java:76) >> at org.apache.commons.dbcp2.DelegatingPreparedStatement.execute >> Query(DelegatingPreparedStatement.java:83) >> at org.apache.commons.dbcp2.DelegatingPreparedStatement.execute >> Query(DelegatingPreparedStatement.java:83) >> >> Caused by: javax.cache.CacheException: class >> org.apache.ignite.IgniteException: Using indexes with different >> parallelism levels in same query is forbidden. >> at org.apache.ignite.internal.processors.cache.IgniteCacheProxy >> .query(IgniteCacheProxy.java:760) >> at org.apache.ignite.internal.jdbc2.JdbcQueryTask.call(JdbcQuer >> yTask.java:161) >> at org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery( >> JdbcStatement.java:116) >> ... 13 more >> 2. query is not returning same result if it is hit number of times. >> >> please let me know if these are known issues. >> >> Thanks >> > > > > -- > Best regards, > Andrey V. Mashenkov > -- Best regards, Andrey V. Mashenkov
