ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Goncharuk <alexey.goncha...@gmail.com>
Subject Re: Cross join bug for partitioned caches
Date Mon, 25 Jan 2016 14:25:55 GMT
Hi Andrey,

You need to properly collocate your data in order to have correct join
results when using partitioned caches (it does not matter whether you join
tables within one partitioned cache or join tables across different
partitioned caches). Please refer to documentation [1] and example [2].
Note the usage of AffinityKey class for Person objects in the example.

An alternative for this approach is to use REPLICATED mode for one of the
caches in the case if this cache contains relatively small data set (so
called star-schema). You can refer to [3] for further details.

As far as I know, this limitation is planned to be removed in ignite-1.6,
however such a distributed join will be significantly slower compared to
collocated join. Stay tuned!

Hope this helps,

[1] https://apacheignite.readme.io/docs/affinity-collocation
[2] org.apache.ignite.examples.datagrid.CacheQueryExample
[3] org.apache.ignite.examples.datagrid.starschema.CacheStarSchemaExample

2016-01-25 17:06 GMT+03:00 Andrey Nestrogaev <a.nestrogaev@flexsoft.com>:

> Hi all!
> Testing ignite 1.5.
> Seems, cross join on partitioned caches, when started more then 1 server
> node return 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-tp2694.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message