cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-233) Serializing the CF name to the sstable for every key is unnecessary
Date Wed, 12 Aug 2009 13:09:15 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742336#action_12742336
] 

Hudson commented on CASSANDRA-233:
----------------------------------

Integrated in Cassandra #165 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/165/])
    Move CFSerializer into its own file.  Rename deserializeEmpty to deserializeFromSSTableNoColumns;
add serializeForSSTable and serializeWithIndexes to do the without-metadata serialization.
 Add SSTableReader.makeColumnFamily to create the CF skeleton w/o reading any data.
patch by jbellis; reviewed by Sandeep Tata for 


> Serializing the CF name to the sstable for every key is unnecessary
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-233
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-233
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.4
>
>         Attachments: 233-rebased.patch, 233.patch
>
>
> Each sstable only contains values from one CF so we ought to be smarter about this. 
(Especially post- CASSANDRA-79, when we include the type and comparator too.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message