ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: affinity key syntax
Date Wed, 25 Oct 2017 10:36:31 GMT
On Wed, Oct 25, 2017 at 3:32 AM, Vladimir Ozerov <vozerov@gridgain.com>

> 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?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message