[
https://issues.apache.org/jira/browse/CASSANDRA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793667#action_12793667
]
Jonathan Ellis commented on CASSANDRA-645:
------------------------------------------
This does use thrift more but (a) that is still better than hand-rolling
serialization, and (b) using strictly the serialization properties means it's
easy to replace with any other serialization lib that supports java; it's the
combination of RPC support and lots of languages that makes it hard to switch
on the client side.
> we need a way to accumulate ColumnFamily objects that contain changes before
> they are committed
that is what Memtable / CF does. the only difference is you need a
CF.add(ThriftMutation) method. Not a big deal.
> and we need a single blob-like thing for the commit log to store
Whatever key-based unit you send to the data nodes, can be re-used here. I
don't see the problem.
> 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.
