Hello,
On Wed, Jul 13, 2016 at 2:26 PM, pragmaticbigdata <[email protected]> wrote: > Following the documentation on data loading > <https://apacheignite.readme.io/docs/data-loading> I have some questions > with regards to ignite version 1.6 > > 1. How does ignite derive the partition id from the cache key? What is the > relation between the partition id and the affinity key? > Affinity function reflect your key to partition. You can get the function using method ignite().affinity(cacheName) > > 2. Partition aware data loading suggests to persist the partition id along > with the data in the database. For this we would need to know the cache key > upfront (as the example indicates - personId) right? How could getting the > key be possible when doing the initial load? Did I misunderstood anything? > You can find partition number using: affinity.partition(key) > > 3. Is the data store implementation called on cluster rebalancing > especially > when a new server node joins the cluster? > Yes it does work. Each node hase own instance of CacheStore. > > Thanks! > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Understanding-data-store-and-partitioning-tp6264.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
