[
https://issues.apache.org/jira/browse/CASSANDRA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-2212:
----------------------------------------
Attachment: 2212_0.6.patch
Attaching patch against 0.6
> Cannot get range slice of super columns in reversed order
> ---------------------------------------------------------
>
> Key: CASSANDRA-2212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2212
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.2
> Environment: Fedore 11, Intel Core i5
> Reporter: Muga Nishizawa
> Assignee: Sylvain Lebresne
> Fix For: 0.7.3
>
> Attachments: 0001-Fix-IndexHelp.indexFor-for-reverse-query.patch,
> 2212_0.6.patch, cassandra_sample_insert.py, cassandra_sample_rangeslice.py,
> create_table.cli
>
> Original Estimate: 6h
> Remaining Estimate: 6h
>
> I cannot get range slice of super columns in reversed order. These data are
> stored in Cassandra in advance. On the other hand, range slice of these data
> in normal order can be acquired.
> You can reproduce the bug by executing attached programs.
> - 1. Start Cassandra daemon on localhost (number of thrift port is 9160)
> - 2. Create keyspace and column family, according to "create_table.cli",
> - 3. Execute "cassandra_sample_insert.py", storing pairs of row keys and
> super columns
> - 4. Execute "cassandra_sample_rangeslice.py" and get range slice of stored
> super columns
> "cassandra_sample_insert.py" and "cassandra_sample_rangeslice.py" require
> pycassa.
> You will need to execute 4."cassandra_sample_rangeslice.py" with following
> options so that you get range slice of super columns in reversed order.
> % python cassandra_sample_rangeslice.py -r 00082 00083
> On the other hand, to get range slice in normal order, you will need to use
> following options.
> % python cassandra_sample_rangeslice.py -f 00082 00083
> 00082 and 00083 are the specified key range. Range slice can be acquired in
> normal order but, I cannot get it in reversed order.
> I assume that there may be a bug within the code for acquiring the index
> block of specified range. In fact, 00083 is included in gap between lastName
> of index block and firstName of next index block.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
