cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-11330) Enable sstabledump to be used on 2i tables
Date Wed, 16 Mar 2016 11:20:33 GMT


Sam Tunnicliffe updated CASSANDRA-11330:
       Resolution: Fixed
    Fix Version/s:     (was: 3.0.x)
                       (was: 3.x)
           Status: Resolved  (was: Patch Available)

Thanks [~yukim], the cassci IRC bot was down when I posted the branches & I forgot to
go back and kick off CI when she returned. Looking at the runs, there are a few unexplained
utest failures on the trunk branch, but there doesn't seem to be anything related to the changes
in any of them. They're all passing for me locally, so I've committed to 3.0 in {{0a5e2204ce74390bfbeb3fa3d74914cf47a13258}}
and merged forward to 3.5 & trunk. I'll keep an eye on the mainline CI builds to make
sure there's nothing to those test failures.


> Enable sstabledump to be used on 2i tables
> ------------------------------------------
>                 Key: CASSANDRA-11330
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 3.0.5, 3.5
> It is sometimes useful to be able to inspect the sstables backing 2i tables, which requires
a small tweak to the way the partitioner is created.
> Although this is an improvement rather than a bugfix, I've marked it for 3.0.x as it's
really very non-invasive.

This message was sent by Atlassian JIRA

View raw message