cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12020) sstablemetadata and sstabledump need better testing
Date Fri, 02 Sep 2016 03:37:20 GMT

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

Chris Lohfink commented on CASSANDRA-12020:
-------------------------------------------

I have a branch at https://github.com/clohfink/cassandra-dtest/tree/12020 with some additional
tests, was going to wait for CASSANDRA-11483 before writing anything for sstablemetadata but
I am not sure its going in. Can include a frozen collections test after CASSANDRA-12594 as
well. wanted to at least put something here while waiting though incase we just want to put
some in.

> sstablemetadata and sstabledump need better testing
> ---------------------------------------------------
>
>                 Key: CASSANDRA-12020
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12020
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tools
>            Reporter: Stefania
>            Assignee: Chris Lohfink
>
> There is one dtest for sstabledump but it doesn't cover sstables with a local partitioner,
which is why a user reported CASSANDRA-12002 on the mailing list; sstablemetadata has no tests
at all, it is only used to check the repair status by repair tests.



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

Mime
View raw message