[
https://issues.apache.org/jira/browse/CASSANDRA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097282#comment-13097282
]
Mck SembWever edited comment on CASSANDRA-3108 at 9/5/11 7:41 PM:
------------------------------------------------------------------
You drastically removed the usage of the {{Range(left, right)}} constructor so
that even the usage of {{intersectionBothWrapping(..)}} and
{{intersectionOneWrapping(..)}} avoids any server-side calls.
In CFIF there AFAIK doesn't seem any other limitation to wrapping ranges...
was (Author: michaelsembwever):
You drastically removed the usage of the {{Range(left, right)}} constructor
so that even the usage of {{intersectionBothWrapping(..)}} and
{{intersectionOneWrapping(..)}} avoids any server-side calls.
It CFIF there AFAIK doesn't seem any other limitation to wrapping ranges...
> Make Range and Bounds objects client-safe
> -----------------------------------------
>
> Key: CASSANDRA-3108
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3108
> 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: http://www.atlassian.com/software/jira
