cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-771) Allow range queries against non-primary nodes for a given range
Date Sat, 06 Feb 2010 04:43:28 GMT


Jonathan Ellis commented on CASSANDRA-771:

minor change: I've edited the comments above the restrictTo call to read

            // make sure we only get keys from the current range (and not other replicas that
might be on the nodes).
            // usually this will be only one range, but sometimes the intersection of a wrapping
Range with a non-wrapping
            // is two disjoint, non-wrapping Ranges separated by a gap.
            List<AbstractBounds> restricted = command.range.restrictTo(currentRange);

> Allow range queries against non-primary nodes for a given range
> ---------------------------------------------------------------
>                 Key: CASSANDRA-771
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.6
>         Attachments: 0001-add-TokenMetadata.ringIterator-to-replace-one-offs-of-.txt,
> Currently any node being down will break range queries that need that node's primary
range, even if RF > 1.

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

View raw message