[
https://issues.apache.org/jira/browse/CASSANDRA-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301894#comment-15301894
]
Sylvain Lebresne commented on CASSANDRA-11877:
----------------------------------------------
I agree with Tyler that trying to have code handle both old an new format is
likely not very easy. I'll also add that we should keep in mind that handling
the pre-3.0 format is somewhat temporary as we want to drop it in 4.0, and so
we don't want to "bend" the non-legacy code so it can play nice with legacy
code. And the more the legacy code is isolated from the rest, the easier it'll
be to remove (which is why we have that big {{LegacyLayout}} class that
segregate the legacy code, even though it's admittedly a tad ugly in theory).
Anyway, agreed with Tyler that copying large parts of the 2.2 code (at least
the {{ColumnIndex}}, possibly more) into the {{LegacyLayout}} class might be
more pragmatic than trying to optimize the amount of code reuse between the 2
formats.
> Add support to legacy row serialization on BigTableWriter
> ---------------------------------------------------------
>
> Key: CASSANDRA-11877
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11877
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tools
> Reporter: Paulo Motta
> Assignee: Kaide Mu
> Priority: Minor
>
> In order to support writing pre-3.0 sstables, we must add support to legacy
> cell serialization to {{BigTableWriter}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
