cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1978) get_range_slices: allow key and token to be interoperable
Date Wed, 26 Jan 2011 15:55:44 GMT


Jonathan Ellis commented on CASSANDRA-1978:

Commented originally on CASSANDRA-2003, but really belongs here:

Let's tighten up ThriftValidation to re-disallow ambiguous queries, e.g., all four of {start_key,
start_token, end_key, end_token}.

Also, please don't change whitespace on lines that are otherwise unchanged, especially when
the change takes us farther from the existing style (e.g., we use a single space around equal
signs, and do not align them with others).

> get_range_slices: allow key and token to be interoperable
> ---------------------------------------------------------
>                 Key: CASSANDRA-1978
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Kelvin Kakugawa
>            Assignee: Kelvin Kakugawa
>            Priority: Minor
>             Fix For: 0.7.2
>         Attachments: 0001-CASSANDRA-1978-allow-key-token-to-be-interoperable-i.patch
> problem: get_range_slices requires two keys or two tokens, so we can't walk a randomly
partitioned cluster by token.
> solution: allow keys and tokens to be mixed.  however, if one side is a token, promote
the bounds to a dht.Range, instead of a dht.Bounds.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message