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 Tue, 02 Aug 2016 14:26:20 GMT

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

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

[~kohlisankalp] We are generally only contributing fixes to 3.0.x now. That said, you could
view the original issue - CASSANDRA-11416 - as a 8099-regression, and in absence of another
way to ignore unknown columns on restore, treat this is a bug fix and commit to 3.0. It's
also a really low-risk change that doesn't modify almost any of the existing code.

We've had this conversation with Jeremiah. So, no, it's not too late. I'll backport unless
there is strong disagreement from somebody.

> 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: client-impacting, doc-impacting, lhf
>             Fix For: 3.10
>
>
> followup from CASSANDRA-6326



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

Mime
View raw message