No error. Just no records is returned, as opposed to the join between the replicated and partitioned cache which returns ass applicable rows. Sorry, for not being clear.
On Mon, May 18, 2020 at 9:00 AM Ilya Kasnacheev <ilya.kasnach...@gmail.com> wrote: > Hello! > > Fails how? Is the result set incorrect? Any specific error message? Please > share details. > > Regards, > -- > Ilya Kasnacheev > > > пн, 18 мая 2020 г. в 16:49, narges saleh <snarges...@gmail.com>: > >> Hi All, >> I have encountered a puzzling join case. >> I have 3 tables on a cluster of two ignite server nodes: >> table-A (id + org = primary), replicated >> id >> org. <-- affinity >> other fields >> >> table-B (id, org, add-id=primary key), partitioned >> id >> org <- affinity >> addr-id >> other fields >> >> table-C (id, org, comp-id=primary key), partitioned >> id >> org <- affinity >> comp-id >> other fields >> >> joins between table-A and table-B (on id, and org) succeeds. >> joins between table-A and table-C (of id and org) succeeds. >> joins between table-B and table-C (on id and org) fails. >> >> all three joins succeed if the cluster has only one server node. >> Why the join between the partitioned caches fail in a distributed mode? >> >> I am using JDBC connection for select statements. The join fails whether >> dealing with thick or thin client. >> >> thanks >> >> >
