[
https://issues.apache.org/jira/browse/CASSANDRA-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401835#comment-13401835
]
Jonathan Ellis commented on CASSANDRA-4357:
-------------------------------------------
- could you split out the non-version-related changes to a separate patch?
- I don't think using MS version is actually adequate to handle, e.g., changing
the checksum type we use internally to the segment. So I think we do need a
separate CL version (which will uniquely identify a MS version, so we don't
need both).
> Add Commitlog Versioning
> ------------------------
>
> Key: CASSANDRA-4357
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4357
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Fix For: 1.2
>
> Attachments: 0001-CASSANDRA-4357.patch
>
>
> Currently when there are changes in protocol version in RowMutation it is not
> handled in the Commit Logs.
> CASSANDRA-4139 adds changes which exposes this.
> It would be nice to reuse MessagingService.currentVersion to be the Commit
> Log version (encoded in the name) instead of creating a separate one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
