You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2014/06/03 19:06:01 UTC

[jira] [Commented] (CASSANDRA-7349) Use Native Frame in CommitLog

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

Benedict commented on CASSANDRA-7349:
-------------------------------------

It's a nice idea in principle, but in practice it's not clear how easy this would be, what with prepared statement context being necessary etc. I'd quite like to be able to do something similar with coordinators dispatching to other nodes, but again this is likely to be a pretty difficult thing to get right. It might be possible to redesign the native protocol and mutation serialization formats at little at some point to help us here, though. Especially once we have enum types for column identifiers.

> Use Native Frame in CommitLog
> -----------------------------
>
>                 Key: CASSANDRA-7349
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7349
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: T Jake Luciani
>              Labels: performance
>             Fix For: 3.0
>
>
> We currently read mutations off the wire then re-serialize them to the commit log.  In the case of the Native protocol we have the native Frame available in the mutation we should be able to special case this and use it in the commit log.  I would expect a decent performance boost.



--
This message was sent by Atlassian JIRA
(v6.2#6252)