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

Make SSTableScanner always respect its bound

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
    • 2.1.5
    • None
    • None

    Description

      When SSTableScanner takes a DataRange, it doesn't fully respect the bounds provided as it always generate a Bounds object, thus potentially ending up including a key it should have excluded. It's currently compensated by in ColumnFamilyStore.getSequentialIterator but that is still an unexpected behavior and is such error prone. We should fix that and remove the compensation in ColumnFamilyStore.getSequentialIterator.

      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
            slebresne Sylvain Lebresne
            Benedict Elliott Smith
            Sylvain Lebresne
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment