Cassandra
  1. Cassandra
  2. CASSANDRA-5514

Track min/max clustered values per sstable to optimize reads

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: 2.0 beta 1
    • Component/s: API, Core
    • Labels:
      None

      Description

      Slice queries can't optimize based on timestamp except for rare cases (CASSANDRA-4116). However, many common queries involve an implicit time component, where the application author knows that he is only interested in data more recent than X, or older than Y.

      We could use the per-sstable max and min timestamps we track to avoid touching cold data if we could pass a hint to Cassandra about the time range we care about.

      1. 0001-CASSANDRA-5514-v1.patch
        42 kB
        Marcus Eriksson
      2. 0001-CASSANDRA-5514-v2.patch
        63 kB
        Marcus Eriksson

        Activity

          People

          • Assignee:
            Marcus Eriksson
            Reporter:
            Jonathan Ellis
            Reviewer:
            Jonathan Ellis
          • Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development