cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Kumar (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-7766) Secondary index not working after a while
Date Mon, 29 Sep 2014 15:00:35 GMT


Shawn Kumar resolved CASSANDRA-7766.
    Resolution: Cannot Reproduce

> Secondary index not working after a while
> -----------------------------------------
>                 Key: CASSANDRA-7766
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: C* 2.1.0-rc5 with small clusters (one or two nodes)
>            Reporter: Fabrice Larcher
>         Attachments: result-failure.txt, result-success.txt
> Since 2.1.0-rc2, it appears that the secondary indexes are not always working. Immediately
after the INSERT of a row, the index seems to be there. But after a while (I do not know when
or why), SELECT statements based on any secondary index do not return the corresponding row(s)
anymore. I noticed that a restart of C* may have an impact (the data inserted before the restart
may be seen through the index, even if it was not returned before the restart).
> Here is a use-case example (in order to clarify my request) :
> {code}
> CREATE TABLE IF NOT EXISTS ( k int PRIMARY KEY, ind ascii, value text);
> INSERT INTO (k, ind, value) VALUES (1, 'toto', 'Hello');
> SELECT * FROM WHERE ind = 'toto'; // Returns no result after a while
> {code}
> The last SELECT statement may or may not return a row depending on the instant of the
request. I experienced that with 2.1.0-rc5 through CQLSH with clusters of one and two nodes.
Since it depends on the instant of the request, I am not able to deliver any way to reproduce
that systematically (It appears to be linked with some scheduled job inside C*).

This message was sent by Atlassian JIRA

View raw message