Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 23 Apr 2014 22:08:20 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12703789.1395859068528.167480.1398290900210@arcas>
In-Reply-To: <JIRA.12703789.1395859068528@arcas>
References: <JIRA.12703789.1395859068528@arcas>
Subject: [jira] [Assigned] (CASSANDRA-6935) Make clustering part of primary
 key a first order component in the storage engine
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedict reassigned CASSANDRA-6935:
-----------------------------------

    Assignee: T Jake Luciani

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