You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michał Michalski (JIRA)" <ji...@apache.org> on 2013/06/06 11:01:27 UTC

[jira] [Commented] (CASSANDRA-5599) Intermittently, CQL SELECT with WHERE on secondary indexed field value returns null when there are rows

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

Michał Michalski commented on CASSANDRA-5599:
---------------------------------------------

To make sure: does it work after recreating index or the problem still happens sometimes?
If it's still failing sometimes:
* Did you try running repair?
* What consistency level do you use for writes and reads?
* How many nodes do you have? 
* Does it happen when you SELECT with CL.CL.ALL?
                
> Intermittently, CQL SELECT  with WHERE on secondary indexed field value returns null when there are rows
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5599
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5599
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.4, 1.2.5
>         Environment: x86_64 / RedHat Enterprise Linux 4.x
>            Reporter: Ravi Basawa
>            Priority: Minor
>
> Intermittently, CQL SELECT  with WHERE on secondary indexed field value returns null when there are rows.
> As it happens intermittently, it is difficult to replicate. To resolve we have had to recreate the index. Also using the nodetool to reindex did not help us either.
> We would create a table, create a secondary index for that table on a field, import data then when we try to select rows from that table with where on said field which should return results, we get a null back ...intermittently.  Sometimes works, sometimes not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira