[
https://issues.apache.org/jira/browse/CASSANDRA-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760487#action_12760487
]
Jonathan Ellis commented on CASSANDRA-456:
------------------------------------------
Belatedly realized this breaks disk compatibility for 0.4 -> 05. Not too bad
though, since clearing out commitlog segments is easily done.
> CommitLog should log RowMutations, not Rows
> -------------------------------------------
>
> Key: CASSANDRA-456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-456
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.4
> Environment: All
> Reporter: Sandeep Tata
> Assignee: Sandeep Tata
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 456.patch
>
>
> Commitlog and Table.apply use Row objects instead of RowMutations. This is an
> unnecessary conversion. Rows are typically used to return results while RM
> should be used for the insert/update/delete path.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
