Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 1 Apr 2011 13:15:05 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1160175083.27955.1301663705835.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <579925621.23292.1301541605727.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (CASSANDRA-2406) Secondary index and index
 expression problems
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis reassigned CASSANDRA-2406:
-----------------------------------------

    Assignee: Jonathan Ellis

> Secondary index and index expression problems
> ---------------------------------------------
>
>                 Key: CASSANDRA-2406
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2406
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.4
>         Environment: CentOS 5.5 (64bit), JDK 1.6.0_23
>            Reporter: Muga Nishizawa
>            Assignee: Jonathan Ellis
>             Fix For: 0.7.5
>
>         Attachments: create_table.cli, secondary_index_checkv2.py, secondary_index_insertv2.py
>
>
> When I iteratively get data with secondary index and index clause, result of data acquired by consistency level "one" is different from the one by consistency level "quorum".  The one by consistecy level "one" is correct result.  But the one by consistecy level "quorum" is incorrect and is dropped by Cassandra.  
> You can reproduce the bug by executing attached programs.
> - 1. Start Cassandra cluster.  It consists of 3 cassandra nodes and distributes data by ByteOrderedPartitioner.  Initial tokens of those nodes are ["31", "32", "33"].  
> - 2. Create keyspace and column family, according to "create_table.cli",
> - 3. Execute "secondary_index_insertv2.py", inserting a few hundred columns to cluster
> - 4. Execute "secondary_index_checkv2.py" and get data with secondary index and index clause iteratively.  "secondary_index_insertv2.py" and "secondary_index_checkv2.py" require pycassa.
> You will be able to execute  4th "secondary_index_checkv2.py" script with following option so that 
> you get data with consistency level "one".  
> % python "secondary_index_checkv2.py" -one
> On the other hand, to acquire data with consistency level "quorum", you will need to use following option.  
> % python "secondary_index_checkv2.py" -quorum
> You can check that result of data acquired by consistency level "one" is different from one by consistency level "quorum".  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira