cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-11877) Add initial support to pre-3.0 sstable serialization
Date Wed, 01 Jun 2016 15:57:59 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310504#comment-15310504
] 

T Jake Luciani edited comment on CASSANDRA-11877 at 6/1/16 3:57 PM:
--------------------------------------------------------------------

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.  This does make it hard
to do though since it this approach was not used in 8099 so the "big" format marker was used
in 2.2 and 3.0.  You could work around this by first releasing a new format marker as part
of a new release in 3.0 for the new format and use "big" only for the old format marker.


was (Author: tjake):
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.  This does make it hard
to do though since it this approach was not used in 8099 so the "big" format marker was used
in 2.2 and 3.0 but you could start by first releasing a new format marker as part of a new
release in 3.0 for the new format and use "big" only for the old format marker.

> 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)

Mime
View raw message