[ https://issues.apache.org/jira/browse/CASSANDRA-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-9638: ---------------------------------------- Component/s: Distributed Metadata > Mirrored distribution tables with same PK > ----------------------------------------- > > Key: CASSANDRA-9638 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9638 > Project: Cassandra > Issue Type: New Feature > Components: Distributed Metadata > Reporter: Constance Eustace > Priority: Major > > CASSANDRA-9231 covers probably most of this... > 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 row. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org