[
https://issues.apache.org/jira/browse/CASSANDRA-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310877#comment-15310877
]
Paulo Motta commented on CASSANDRA-11877:
-----------------------------------------
bq. I'm chiming in to suggest that you should consider maintaining two formats
using CASSANDRA-7443 vs maintaining the LegacyLayout class inside of the
bigtable format.
Thanks for the suggestion [~tjake]. We want to go that route ultimately, but
for simplicity instead of using a different format we will initially use the
version string within BigFormat to choose which {{BigTableWriter}}
implementation to pick on {{SSTableFormat.getWriterFactory}} (if current
{{BigTableWriter}} or {{LegacyBigTableWriter}}), so we focus on the data
conversions now and don't get distracted with other changes to support that
(such as supporting multi-format reads, etc), but we will definitely want to
revisit this, possibly in a separate task.
> Add initial support to pre-3.0 sstable serialization
> ----------------------------------------------------
>
> 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, the easiest route is to port
> pre-3.0 {{BigTableWriter}} to {{LegacyLayout}}, so it can be easily removed
> when this support is removed in the next majorversion.
> For simplicity, we should consider only the simple case in this ticket: no
> range tombstones and index sampling. We can add support to those in follow-up
> tickets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
