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

Ability for CQL3 to list partition keys

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Fix Version/s: 2.0.1
    • Component/s: CQL
    • Labels:

      Description

      It can be useful to know the set of in-use partition keys (storage engine row keys). One example given to me was where application data was modeled as a few 10s of 1000s of wide rows, where the app required presenting these rows to the user sorted based on information in the partition key. The partition count is small enough to do the sort client-side in memory, which is what the app did with the Thrift API--a range slice with an empty columns list.

      This was a problem when migrating to CQL3. SELECT mykey FROM mytable includes all the logical rows, which makes the resultset too large to make this a reasonable approach, even with paging.

      One way to add support would be to allow DISTINCT in the special case of SELECT DISTINCT mykey FROM mytable.

        Attachments

        1. 4536.txt
          13 kB
          Aleksey Yeschenko
        2. cassandra-4536_1.1.0.patch
          8 kB
          dan jatnieks
        3. cassandra-4536_1.2.2.patch
          107 kB
          dan jatnieks
        4. cassandra-4536_1.2.5.patch
          8 kB
          dan jatnieks

          Activity

            People

            • Assignee:
              iamaleksey Aleksey Yeschenko
              Reporter:
              jbellis Jonathan Ellis
              Reviewer:
              Sylvain Lebresne
            • Votes:
              7 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: