ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christos Erotocritou <chris...@gridgain.com>
Subject Non-collocated distributed SQL Joins across caches over separate cluster groups
Date Wed, 05 Apr 2017 09:02:01 GMT

Is it correct to assume the following:
We have an Ignite cluster comprised of 2 cluster groups A & B that have different caches
We use an Ignite client to obtain API access to the whole cluster and execute a join query
that joins data across the 2 caches 
My understanding is that this is not possible, correct? 

Reading this article [1 <https://dzone.com/articles/how-apache-ignite-helped-a-large-bank-process-geog-1>]
it seems that such cross-cluster-group behaviour is supported with the transactions API and
also advised.

Any thoughts why the SQL API would not allow this and requires caches to be located on all
nodes when the JOIN query is executed?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message