cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Constance Eustace (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-9638) Mirrored distribution tables with same PK
Date Tue, 23 Jun 2015 16:59:00 GMT
Constance Eustace created CASSANDRA-9638:

             Summary: Mirrored distribution tables with same PK
                 Key: CASSANDRA-9638
             Project: Cassandra
          Issue Type: New Feature
          Components: Core
            Reporter: Constance Eustace

Many of the problems with CAP and cross-partition data seems to deal with the data not being
local across partitions. 

Shouldn't it be possible to provide a mechanism where associated or "child" data gets mapped
in the same data distribution pattern as the parent key/table, even in Vnodes?

Certainly if the PK is exactly the same (extension tables or the like). And while schema could
technically be centralized in the same rowkey, in reality the "sweet spot" of columns / partition
key gets in the way of this. 

It would be super tough mathematically to do the same distribution for PKs that are something
like PK: {parentkey, extensionkey) and get that to hash/distribute the same, but that would
be nice, but perhaps an expansion of key lookup to calculate "distribution/vnode key that
maps to the distribution range, and then an actual lookup key in the node for the actual partition

This message was sent by Atlassian JIRA

View raw message