cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3108) Make Range and Bounds objects client-safe
Date Tue, 06 Sep 2011 21:29:11 GMT


Jonathan Ellis commented on CASSANDRA-3108:

bq. even the usage of intersectionBothWrapping(..) and intersectionOneWrapping(..) avoids
any server-side calls

Right.  What I don't follow is how this changes behavior of allowing wrapping ranges?

> Make Range and Bounds objects client-safe
> -----------------------------------------
>                 Key: CASSANDRA-3108
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.8.2
>            Reporter: Jonathan Ellis
>            Assignee: Mck SembWever
>              Labels: hadoop
>             Fix For: 0.8.5
>         Attachments: 3108.txt
> From Mck's comment on CASSANDRA-1125:
> Something broke here in production once we went out with 0.8.2. It may have been some
poor testing, i'm not entirely sure and a little surprised.
> CFIF:135 breaks because inside dhtRange.intersects(jobRange) there's a call to new Range(token,
token) which calls StorageService.getPartitioner() and StorageService is null as we're not
inside the server.
> A quick fix is to change Range:148 from new Range(token, token) to new Range(token, token,
partitioner) making the presumption that the partitioner for the new Range will be the same
as this Range.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message