Re: [infinispan-dev] [ISPN-78] Alternative interface for writing large objects

> > 3. The design suggests to use a fresh UUID as the key for each new > > chunk. While this in all likelihood gives us a unique new key for each > > chunk I currently fail to see how that guarantees that this key maps to > > a node that is different from all the nodes already used to store chunks > > of the same Large Object. But then again I know next to nothing about > > Infinispan's constant hashing algorithm. > > I think there's a service that will generate a key mapped to particular > node, so that might be a better option here to avoid all chunks going to the > same node. I think Mircea might be able to help further with this. Implemented a workaround in the meantime. Would be fab if such a service existed. Haven't found it yet.