Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1984796262.1261438398504.JavaMail.jira@brutus>
Date: Mon, 21 Dec 2009 23:33:18 +0000 (UTC)
From: "Gary Dusbabek (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-645) replace RowMutation w/ serialized
 thrift structs
In-Reply-To: <91949514.1261165098174.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gary Dusbabek commented on CASSANDRA-645:
-----------------------------------------

I still don't get where the extra copy is happening.  Are you referring to serialization/deserialization operations?  Do you mean that the creation of RowMutation should be pushed down to be as near to the actual write as possible?

> replace RowMutation w/ serialized thrift structs
> ------------------------------------------------
>
>                 Key: CASSANDRA-645
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-645
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.9
>
>         Attachments: 645-thrift.patch
>
>
> using the client's representation internally will save basically a copy operation on the critical write path

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