On Wed, Oct 25, 2017 at 3:32 AM, Vladimir Ozerov <voze...@gridgain.com> wrote:
> Dima, > > Yes, I saw it also. But this is not about syntax only. Spanner use this > information to store data efficiently - child entries a located near to > their parents. We can think of it as if all related tables were logical > caches inside one physical cache, sorted by the key. With this storage > format it will be possible to implement very efficient co-located joins. > Hm... I don't think Ignite's approach for collocated joins is lees efficient. However, back to Spanner, the first value in the child table key is the parent table key. This tells me that Spanner collocates based on an approach very similar to Ignite's affinity key. Am I wrong?
