Hi, On Wed, Jul 13, 2016 at 3:48 PM, pragmaticbigdata <[email protected]> wrote:
> > You can find partition number using: affinity.partition(key) > > My question was - to get the partition id we need the cache key. When doing > the initial load into ignite we don't have the cache key. Does that mean we > cannot have an optimized data loading (i.e. partition aware data loading)? > Cache is a key-value store at first. Yes you can to use ID of record (from database), as key of cache. > > > Yes it does work. Each node hase own instance of CacheStore. > > Is the loadCache() method from the CacheStore invoked on a new server node > that joins the cluster? If yes, what is the reason behind it? Won't it be > copying the existing partitions from other server nodes? > If node joined after the method (loadCache) was executed, then partitions will by relocated to new node (with all data in it). > > Thanks > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Understanding-data-store-and-partitioning-tp6264p6272.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
