[ https://issues.apache.org/jira/browse/CASSANDRA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094160#comment-13094160 ]
Hudson commented on CASSANDRA-3108: ----------------------------------- Integrated in Cassandra-0.8 #305 (See [https://builds.apache.org/job/Cassandra-0.8/305/]) make Range and Bounds objects client-safe patch by Mck SembWever and jbellis for CASSANDRA-3108 jbellis : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1163394 Files : * /cassandra/branches/cassandra-0.8/CHANGES.txt * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/dht/Bounds.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/dht/Range.java > 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