You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2016/05/25 22:23:12 UTC
[jira] [Commented] (CASSANDRA-11877) Add support to legacy row
serialization on BigTableWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300988#comment-15300988 ]
Tyler Hobbs commented on CASSANDRA-11877:
-----------------------------------------
bq. Make LegacyCell implement Unfiltered, so we can treat legacy and non-legacy partition uniformly on ColumnIndex.add
I'm not sure that's going to work well. A {{LegacyCell}} is simply one cell, not a row, so it seems like there are going to be some conceptual mismatches.
It's also worth noting that the on-wire serialization is different from the on-disk serialization format. In particular, range tombstones are handled differently (see {{ColumnIndex.add()}} and {{ColumnIndex.build()}} in 2.2). It may be simplest (although still nasty) to try to port the 2.2 version of {{ColumnIndex}} to 3.0 using the {{Legacy}} classes, because the logic is quite a bit different than the 3.0 logic.
> 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)