cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7190) Add schema to snapshot manifest
Date Fri, 20 May 2016 14:52:12 GMT

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

Aleksey Yeschenko commented on CASSANDRA-7190:
----------------------------------------------

bq. With the caveat that we can't express the drop informations with a CQL statements, and
as we've noted, that's important for a snapshot. Unless we do add some kind of WITH TIMESTAMP
to ALTER DROP that is (which I don't love-love but might be the most pragmatic answer in practice).

Yeah. Can't say I liked it when I proposed it first, or that I like it still, either. So either
we do that, or, alternatively, we add a way to load the schema snapshot via other means (load
JSON/YAML encoded full schema - including dropped columns - via JMX?, get it all applied in
batch, then proceed with restoring the backups).

> Add schema to snapshot manifest
> -------------------------------
>
>                 Key: CASSANDRA-7190
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7190
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jonathan Ellis
>            Assignee: Alex Petrov
>            Priority: Minor
>              Labels: lhf
>             Fix For: 3.x
>
>
> followup from CASSANDRA-6326



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message