Hello, I must apologize, it's my bad. Indexes weren't created
Shame on me and thanks for help :)
Le jeu. 18 avr. 2019 à 16:18, Maxim.Pudov a écrit :
> By default Ignite thinks that data is collocated. You have to tell Ignite
> that it is not. For example, by adding a parameter to JDBC con
By default Ignite thinks that data is collocated. You have to tell Ignite
that it is not. For example, by adding a parameter to JDBC connection:
distributedJoins=true or by using this method
SqlQueryFields.setDistributedJoins [1] in java API.
[1]
https://ignite.apache.org/releases/latest/javadoc/o
Sorry for short answer.
Document just say that if the join condition is not pk or affinity, it
broadcast request instead of unicast.
In my case, i use indexed columns, but I receive exception.
Regards
Le mer. 17 avr. 2019 à 18:36, yann Blazart a
écrit :
> Hi. Thanks for answer.
>
> But it doe
Hi. Thanks for answer.
But it doesn't explain my case
Le mer. 17 avr. 2019 à 16:56, Maxim.Pudov a écrit :
> Hi, check out this article:
>
> https://apacheignite-sql.readme.io/docs/distributed-joins#section-non-collocated-joins
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.c
Hi, check out this article:
https://apacheignite-sql.readme.io/docs/distributed-joins#section-non-collocated-joins
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello, I really need help.
First, sorry but I can’t share code because of my boss.
I have two tables, normally partitioned, but I can’t collocate data (simply
because other tables are related to using other columns).
On these tables I have stetted my indexes, everything is done using create
tabl
