[ https://issues.apache.org/jira/browse/CASSANDRA-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254171#comment-14254171 ]
Pavel Baranov edited comment on CASSANDRA-8526 at 12/19/14 10:52 PM: --------------------------------------------------------------------- It looks like I found a solution (sorry, I should've done the trace earlier) but it seems like "nodetool rebuild_index ...." didn't do anything, however, once I did "drop index updated_date;" and then "CREATE INDEX updated_date ON tweets.tweets_updated (updated_date);" the query started working (returning results). So maybe it's just nodetool issue? Thank you! p.s. also the original not working query was based on "updated_date" and not on "updated" - it was a typo. was (Author: rookie7799): It looks like I found a solution (sorry, I should've done the trace earlier) but it seems like "nodetool rebuild_index ...." didn't do anything, however, once I did "drop index updated_date;" and then "CREATE INDEX updated_date ON tweets.tweets_updated (updated_date);" the query started working (returning results). So maybe it's just nodetool issue? Thank you! > Query on a secondary index stopped working > ------------------------------------------ > > Key: CASSANDRA-8526 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8526 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: CentOS release 6.5 > cassandra21-2.1.2-1.noarch > Reporter: Pavel Baranov > > After upgrading from cassandra 2.0.10 to 2.1.2 this type of query (using > cqlsh) on a secondary index have stopped working (not returning results): > {noformat} > select * from tweets_updated where updated = '2014-09-06' limit 1; > {noformat} > However the data exists: > {noformat} > select * from tweets_updated limit 5; > uname | updated | updated_date > -----------------+--------------------------+-------------- > xxxxxx1 | 2014-08-22 17:37:46-0700 | null > xxxxxx2 | null | 2014-09-06 > {noformat} > There are two secondary indexes: > {noformat} > CREATE TABLE tweets.tweets_updated ( > uname text PRIMARY KEY, > updated timestamp, > updated_date text > ) WITH bloom_filter_fp_chance = 0.01 > AND caching = '{"keys":"ALL", "rows_per_partition":"NONE"}' > AND comment = '' > AND compaction = {'min_threshold': '4', 'class': > 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy', > 'max_threshold': '32'} > AND compression = {'sstable_compression': > 'org.apache.cassandra.io.compress.LZ4Compressor'} > AND dclocal_read_repair_chance = 0.0 > AND default_time_to_live = 0 > AND gc_grace_seconds = 864000 > AND max_index_interval = 2048 > AND memtable_flush_period_in_ms = 0 > AND min_index_interval = 128 > AND read_repair_chance = 0.1 > AND speculative_retry = '99.0PERCENTILE'; > CREATE INDEX tweets_updated_updated_idx ON tweets.tweets_updated (updated); > CREATE INDEX updated_date ON tweets.tweets_updated (updated_date); > {noformat} > I've run nodetool rebuild_index on both of them after upgrade - did not help. -- This message was sent by Atlassian JIRA (v6.3.4#6332)