[
https://issues.apache.org/jira/browse/CASSANDRA-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedict resolved CASSANDRA-6935.
---------------------------------
Resolution: Later
I think sylvain will be introducing some tickets that should encompass this
change in the near future, so I'll close this in favour of those future
discussions.
> Make clustering part of primary key a first order component in the storage
> engine
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-6935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6935
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
> Assignee: T Jake Luciani
> Labels: performance
> Fix For: 3.0
>
>
> It would be helpful for a number of upcoming improvements if the clustering
> part of the primary key were extracted from CellName, and if a ColumnFamily
> object could store multiple ClusteredRow (or similar) instances, within which
> each cell is keyed only by the column identifier.
> This would also, by itself, reduce on comparison costs and also permit memory
> savings in memtables, by sharing the clustering part of the primary key
> across all cells in the same row. It might also make it easier to move more
> data off-heap, by constructing an off-heap clustered row, but keeping the
> partition level object on-heap.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
