Since a replicated cache has an entire copy of all its data on each server
node, the data is local so you can join to it is my understanding.
From: Clay Teahouse
Sent: Tuesday, January 19, 2021 9:49 AM
To: user@ignite.apache.org
Subject: Join between replicated and partitioned caches
CAUTION: T
Can you provide the query and the explain plan of the query (via Ignite Web
Console)?
First step I would suggest is to seek to tune the query, maybe it needs an
index, or the driving table needs to be changed, or maybe the query uses
indexes correctly but many rows are returned from the driving
e such
queries.
Somewhere I have seen below few properties for the same, are those not
available in Ignite open source?
1. sqlQueryMemoryQuota
2. sqlOffloadingEnabled
3. sqlGlobalMemoryQuota
Thanks and Regards,
Kamlesh Joshi
From: Craig Gresbrink
mailto:cgresbr...@24hourfit.com>&
Is table c, a child of table b?
You have:
tbl_a tbl_b tbl_c
--- -
aff_a aff_b
You want:
tbl_a tbl_b tbl_c
--- -
aff_a aff_a
You want a "cosmic parent" in this case it see
I am making a fair amount of assumptions:
1. aff_b means that table c has an affinity key that includes table b's id
plus table c's id. Is that true?
2. I get that table c has a foreign key to table b.
3. You are doing puts to your caches, then use the sql query engine with
distjoins=fa
