cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Created: (CASSANDRA-1722) Index scan only ever scans first node in ring
Date Wed, 10 Nov 2010 03:21:23 GMT
Index scan only ever scans first node in ring

                 Key: CASSANDRA-1722
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 0.7 beta 3
            Reporter: Jonathan Ellis
             Fix For: 0.7.0

        List<AbstractBounds> ranges = getRestrictedRanges(new Bounds(leftToken, p.getMinimumToken()));

when called with empty start key this means we have a Bounds(minToken, minToken), which hits
the getRR special case

        // special case for bounds containing exactly 1 token
        if (queryRange instanceof Bounds && queryRange.left.equals(queryRange.right))
            if (logger.isDebugEnabled())
                logger.debug("restricted single token match for query " + queryRange);
            return Collections.singletonList(queryRange);

Looks like this broke as a side effect of CASSANDRA-1442.  Prior to that a bounds from [T,
minToken] was considered "up to infinity" by getRR so would span multiple nodes.

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

View raw message