Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 15 Sep 2016 18:43:20 +0000 (UTC)
From: "Tyler Hobbs (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12875427.1442511249000.583062.1473965000773@Atlassian.JIRA>
In-Reply-To: <JIRA.12875427.1442511249000@Atlassian.JIRA>
References: <JIRA.12875427.1442511249000@Atlassian.JIRA> <JIRA.12875427.1442511249875@arcas>
Subject: [jira] [Updated] (CASSANDRA-10364) Improve test coverage for schema
 tables and document 3.0 changes to schema tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 15 Sep 2016 18:43:22 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-10364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tyler Hobbs updated CASSANDRA-10364:
------------------------------------
    Reviewer:   (was: Tyler Hobbs)

> Improve test coverage for schema tables and document 3.0 changes to schema tables
> ---------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10364
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10364
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>             Fix For: 3.0.x
>
>
> In particular,
> {{LegacySchemaMigratorTest.java}}:
>     Needed test coverage:
>         Legacy schema tables are removed
>         New schema tables are written to with the correct timestamp
>         Legacy schema tables don't exist in new schema tables
>         Migrating tables in general, especially COMPACT ones
>             Null values for any optional fields
>         Maybe UDTs that refer to other UDTs?
>         NTS keyspaces
> Similar coverage is also important to have for {{SchemaKeyspace}}, with no migration involved.


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