Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4EF7B10483 for ; Fri, 19 Dec 2014 22:39:14 +0000 (UTC) Received: (qmail 95564 invoked by uid 500); 19 Dec 2014 22:39:14 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 95536 invoked by uid 500); 19 Dec 2014 22:39:14 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 95525 invoked by uid 99); 19 Dec 2014 22:39:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Dec 2014 22:39:14 +0000 Date: Fri, 19 Dec 2014 22:39:14 +0000 (UTC) From: "Tyler Hobbs (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-8526) Query on a secondary index stopped working MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Hobbs updated CASSANDRA-8526: ----------------------------------- Description: 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. was: 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): select * from tweets_updated where updated_date = '2014-09-06' limit 1; However the data exists: select * from tweets_updated limit 5; uname | updated | updated_date -----------------+--------------------------+-------------- xxxxxx1 | 2014-08-22 17:37:46-0700 | null xxxxxx2 | null | 2014-09-06 There are two secondary indexes: 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); I've run nodetool rebuild_index on both of them after upgrade - did not help. > 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)