You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/06/01 17:16:23 UTC

[jira] [Commented] (CASSANDRA-4262) 1.1 does not preserve compatibility w/ index queries against 1.0 nodes

    [ https://issues.apache.org/jira/browse/CASSANDRA-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287470#comment-13287470 ] 

Jonathan Ellis commented on CASSANDRA-4262:
-------------------------------------------

Can we do something to make the problem more obvious when someone does a seq-scan-with-filters in a mixed-version cluster, than just send the RSC and have it error out?  Even just logging WARN would be better than nothing.
                
> 1.1 does not preserve compatibility w/ index queries against 1.0 nodes
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-4262
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4262
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>            Priority: Critical
>             Fix For: 1.1.1
>
>         Attachments: 4262.txt
>
>
> 1.1 merged index + seq scan paths into RangeSliceCommand.  1.1 StorageProxy always sends a RSC for either scan type.  But 1.0 RSVH only does seq scans.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira