> > I still want to know why you choose T3 for partition mode, why not T2 or > T1, > is there any rules?
Because all T1 and T2 data will be available on the any node in the cluster (REPLICATED) T3 cache can be distributed between cluster nodes (PARTITIONED) and provide required colocation. On Thu, Nov 5, 2015 at 3:22 PM, iceguo <[email protected]> wrote: > Sorry for reply late. > > Table T1 and T2 have no primary key originally. > > Before putting entries into cache, I manually added to the table a column > "ID" for primary key. > > Then I use ignite-schema-import to generate Java domain model POJOs. > > I still want to know why you choose T3 for partition mode, why not T2 or > T1, > is there any rules? > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/The-result-of-cross-cache-SQL-joins-is-incomplete-tp1723p1850.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Andrey Gura GridGain Systems, Inc. www.gridgain.com
