cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-9699) Make choice of sstable reader types explicit
Date Wed, 01 Jul 2015 15:50:04 GMT
Benedict created CASSANDRA-9699:

             Summary: Make choice of sstable reader types explicit
                 Key: CASSANDRA-9699
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: Benedict
            Assignee: Benedict
             Fix For: 3.0.0 rc1

CASSANDRA-9580 made it apparent that the efforts to isolate unsafe users of early opened results
wasn't quite fully successful. 

This patch attempts to impose some minor central refactors that force the (internal) user
to specify if they want the live sstable set, or the "canonical" sstable set (or just the
"noncompacting" set, since this is the intersection of the two). It also eliminates a lot
of ugliness and some duplication around filtration, and obsoletes the CANONICAL_SSTABLES and
UNREPAIRED_SSTABLES functions in ColumnFamilyStore, which were very ugly.

This message was sent by Atlassian JIRA

View raw message