Exactly, I have faced the same problem and posted this question to the forum, not yet got any response.
Thanks On 12-Dec-2017 1:48 PM, "Ahmad Al-Masry" <ma...@harri.com> wrote: > Hi; > I added @AffinityKeyMapped to the fields in the model generated by web > console. > But I also noticed that when I load the data using the load > commands generated from the web console, the data is not collocated and the > query will return reduced data. > Do you have any hints? > BR > > > On Dec 11, 2017, at 3:12 PM, Nikolai Tikhonov <ntikho...@apache.org> > wrote: > > It depends from your data model and can't be enabled via one property. > Please, look at the following documentation pages: > > https://apacheignite.readme.io/docs/affinity-collocation > https://apacheignite-sql.readme.io/docs/distributed-joins#collocated-joins > > On Mon, Dec 11, 2017 at 4:02 PM, Ahmad Al-Masry <ma...@harri.com> wrote: > >> How can I enable this on the server configuration XML? >> BR >> >> >> On Dec 11, 2017, at 2:31 PM, Nikolai Tikhonov <ntikho...@apache.org> >> wrote: >> >> Hi, >> >> Strongly recommend to care about collocation of your data (as above >> suggested by Vlad) instead of enable DistributedJoins flag. The performance >> of this type of joins is worse then the performance of the affinity >> collocation based joins due to the fact that there will be much more >> network round-trips and data movement between the nodes to fulfill a query >> [1]. >> >> 1. https://apacheignite-sql.readme.io/docs/distributed-joins >> #non-collocated-joins >> >> >> On Mon, Dec 11, 2017 at 3:03 PM, Ahmad Al-Masry <ma...@harri.com> wrote: >> >>> Hi; >>> When I enabled the distributed JOIN, get the following Exception: >>> >>> java.sql.SQLException: javax.cache.CacheException: Failed to prepare >>> distributed join query: join condition does not use index >>> [joinedCache=PositionTypeCache >>> >>> Should I remove the indexes before doing distributed joins? >>> BR >>> >>> >>> On Dec 11, 2017, at 10:43 AM, Vladislav Pyatkov <vldpyat...@gmail.com> >>> wrote: >>> >>> Hi, >>> >>> When you use JOIN, you should to enable DistributedJoins flag[1], or >>> tack care about collocated of each joined entry[2]. >>> >>> [1]: org.apache.ignite.cache.query.SqlFieldsQuery#setDistributedJoins >>> [2]: https://apacheignite.readme.io/docs >>> >>> On Mon, Dec 11, 2017 at 11:36 AM, Ahmad Al-Masry <ma...@harri.com> >>> wrote: >>> >>>> Dears; >>>> The when I execute the attached query on Mysql data source or on a >>>> single node ignite, it returns about 25k records. >>>> When multiple node, it gives me about 3500 records. >>>> The caches are atomic and partitioned. >>>> Any suggestions. >>>> BR >>>> >>>> -- >>>> >>>> >>>> >>>> This email, and the content it contains, are intended only for the >>>> persons >>>> or entities to which it is addressed. It may contain sensitive, >>>> confidential and/or privileged material. Any review, retransmission, >>>> dissemination or other use of, or taking of any action in reliance upon, >>>> this information by persons or entities other than the intended >>>> recipient(s) is prohibited. If you received this email in error, please >>>> immediately contact security[at]harri[dot]com and delete it from any >>>> device >>>> or system on which it may be stored. >>>> >>> >>> >>> >>> -- >>> Vladislav Pyatkov >>> >>> >>> >>> >>> This email, and the content it contains, are intended only for the >>> persons or entities to which it is addressed. It may contain sensitive, >>> confidential and/or privileged material. Any review, retransmission, >>> dissemination or other use of, or taking of any action in reliance upon, >>> this information by persons or entities other than the intended >>> recipient(s) is prohibited. If you received this email in error, please >>> immediately contact security[at]harri[dot]com and delete it from any device >>> or system on which it may be stored. >>> >> >> >> >> >> This email, and the content it contains, are intended only for the >> persons or entities to which it is addressed. It may contain sensitive, >> confidential and/or privileged material. Any review, retransmission, >> dissemination or other use of, or taking of any action in reliance upon, >> this information by persons or entities other than the intended >> recipient(s) is prohibited. If you received this email in error, please >> immediately contact security[at]harri[dot]com and delete it from any device >> or system on which it may be stored. >> > > > > > This email, and the content it contains, are intended only for the persons > or entities to which it is addressed. It may contain sensitive, > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended > recipient(s) is prohibited. If you received this email in error, please > immediately contact security[at]harri[dot]com and delete it from any device > or system on which it may be stored. >
