Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BD123200A5B for ; Wed, 25 May 2016 21:10:55 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BBB7B160A29; Wed, 25 May 2016 19:10:55 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 10544160A0F for ; Wed, 25 May 2016 21:10:54 +0200 (CEST) Received: (qmail 77407 invoked by uid 500); 25 May 2016 18:59:13 -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 77323 invoked by uid 99); 25 May 2016 18:59:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 May 2016 18:59:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id EAFFD2C1F62 for ; Wed, 25 May 2016 18:59:12 +0000 (UTC) Date: Wed, 25 May 2016 18:59:12 +0000 (UTC) From: "Tyler Hobbs (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-11473) Clustering column value is zeroed out in some query results MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 25 May 2016 19:10:55 -0000 [ https://issues.apache.org/jira/browse/CASSANDRA-11473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300654#comment-15300654 ] Tyler Hobbs commented on CASSANDRA-11473: ----------------------------------------- Since I haven't been able to reproduce this, and I don't have any more hypotheses as to the cause, I'm going to close this for now as Cannot Reproduce. If anybody else hits a similar problem or has any idea, please feel free to comment. > Clustering column value is zeroed out in some query results > ----------------------------------------------------------- > > Key: CASSANDRA-11473 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11473 > Project: Cassandra > Issue Type: Bug > Environment: debian jessie patch current with Cassandra 3.0.4 > Reporter: Jason Kania > Assignee: Tyler Hobbs > > As per a discussion on the mailing list, http://www.mail-archive.com/user@cassandra.apache.org/msg46902.html, we are encountering inconsistent query results when the following query is run: > {noformat} > select "subscriberId","sensorUnitId","sensorId","time" from > "sensorReadingIndex" where "subscriberId"='JASKAN' AND "sensorUnitId"=0 AND "sensorId"=0 ORDER BY "time" LIMIT 10; > {noformat} > Invalid Query Results > {noformat} > subscriberId sensorUnitId sensorId time > JASKAN 0 0 2015-05-24 2:09 > JASKAN 0 0 1969-12-31 19:00 > JASKAN 0 0 2016-01-21 2:10 > JASKAN 0 0 2016-01-21 2:10 > JASKAN 0 0 2016-01-21 2:10 > JASKAN 0 0 2016-01-21 2:11 > JASKAN 0 0 2016-01-21 2:22 > JASKAN 0 0 2016-01-21 2:22 > JASKAN 0 0 2016-01-21 2:22 > JASKAN 0 0 2016-01-21 2:22 > {noformat} > Valid Query Results > {noformat} > subscriberId sensorUnitId sensorId time > JASKAN 0 0 2015-05-24 2:09 > JASKAN 0 0 2015-05-24 2:09 > JASKAN 0 0 2015-05-24 2:10 > JASKAN 0 0 2015-05-24 2:10 > JASKAN 0 0 2015-05-24 2:10 > JASKAN 0 0 2015-05-24 2:10 > JASKAN 0 0 2015-05-24 2:11 > JASKAN 0 0 2015-05-24 2:13 > JASKAN 0 0 2015-05-24 2:13 > JASKAN 0 0 2015-05-24 2:14 > {noformat} > Running the following yields no rows indicating that the 1969... timestamp is invalid. > {noformat} > select "subscriberId","sensorUnitId","sensorId","time" FROM "edgeTransitionIndex" where "subscriberId"='JASKAN' AND "sensorUnitId"=0 AND "sensorId"=0 and time='1969-12-31 19:00:00-0500'; > {noformat} > The schema is as follows: > {noformat} > CREATE TABLE sensorReading."sensorReadingIndex" ( > "subscriberId" text, > "sensorUnitId" int, > "sensorId" int, > time timestamp, > "classId" int, > correlation float, > PRIMARY KEY (("subscriberId", "sensorUnitId", "sensorId"), time) > ) WITH CLUSTERING ORDER BY (time ASC) > AND bloom_filter_fp_chance = 0.01 > AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'} > AND comment = '' > AND compaction = {'class': 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy', 'max_threshold': '32', 'min_threshold': '4'} > AND compression = {'chunk_length_in_kb': '64', 'class': 'org.apache.cassandra.io.compress.LZ4Compressor'} > AND crc_check_chance = 1.0 > AND dclocal_read_repair_chance = 0.1 > 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.0 > AND speculative_retry = '99PERCENTILE'; > CREATE INDEX classSecondaryIndex ON sensorReading."sensorReadingIndex" ("classId"); > {noformat} > We were asked to provide our sstables as well but these are very large and would require some data obfuscation. We are able to run code or scripts against the data on our servrers if that is option. -- This message was sent by Atlassian JIRA (v6.3.4#6332)