Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-9699

Make choice of sstable reader types explicit

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 3.0 alpha 1
    • None
    • None

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            benedict Benedict Elliott Smith Assign to me
            benedict Benedict Elliott Smith
            Benedict Elliott Smith
            Marcus Eriksson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment