-bug-for-partitioned-caches-tp2694p2728.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
-ignite-users.70518.x6.nabble.com/Cross-join-bug-for-partitioned-caches-tp2694.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
n incorrect result (part of the rows is missing).
>
> When started only one server node or caches in replicated mode all work
> correctly.
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Cross-join-bug-for-partitioned-caches-tp26
If you need an ability to run ad-hoc SQL, then you're right and you need to
have one PARTITIONED cache and all others should be REPLICATED. However, if
you know your SQL queries in advance, usually you can some up with a
collocation strategy for multiple PARTITIONED caches.
I believe the
t;:
> Hi Alexey,
>
> "Cross Join" doesn't imply predicates for table joins, so how can
> collocation help with this type of join?
>
> Only workaround is to have all caches in repliacted mode except one.
>
>
>
> --
> View this message in context:
>
/affinity-collocation
[2]
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheQueryExample.java
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cross-join-bug-for-partitioned-caches-tp2694p2709.html
Sent
