You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2012/06/01 17:58:23 UTC
[jira] [Updated] (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:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-4262:
----------------------------------------
Attachment: 4262-v2.txt
Actually, I'm wrong. We do allow seq-scan-with-filters on the thrift side. So anyway, attaching a v2 that does throw an exception in that case on the sending node.
Still leave the question if we should allow those sequential queries with filters in CQL3 I guess.
> 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-v2.txt, 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