[
https://issues.apache.org/jira/browse/CASSANDRA-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139275#comment-15139275
]
Yuki Morishita commented on CASSANDRA-10583:
--------------------------------------------
[~depend] Thanks for the report.
I used your repository and generated SSTable, create 1 node cassandra cluster
for v2.1.9 and the latest cassandra-2.1, and loaded generated SSTable using
sstableloader.
Unfortunately, I could not reproduce your issue in both clusters.
{code}
cqlsh:timeseries_test> select * from double_daily where tag='TEST' and group =
1 and timestamp > '2002-05-05 00:00:00-0400';
tag | group | timestamp | value
------+-------+--------------------------+-------
TEST | 1 | 2002-05-05 05:00:00+0000 | 4
TEST | 1 | 2002-05-06 05:00:00+0000 | 5
TEST | 1 | 2002-05-07 05:00:00+0000 | 6
TEST | 1 | 2002-05-08 05:00:00+0000 | 7
TEST | 1 | 2002-05-09 05:00:00+0000 | 8
TEST | 1 | 2002-05-10 05:00:00+0000 | 9
(6 rows)
{code}
The result of {{sstable2json}} does not seem problematic.
{code}
[
{"key": "TEST",
"cells": [["1:2002-05-01 00\\:00-0500:","",1455036610854000],
["1:2002-05-01 00\\:00-0500:value","0.0",1455036610854000],
["1:2002-05-02 00\\:00-0500:","",1455036610861000],
["1:2002-05-02 00\\:00-0500:value","1.0",1455036610861000],
["1:2002-05-03 00\\:00-0500:","",1455036610861000],
["1:2002-05-03 00\\:00-0500:value","2.0",1455036610861000],
["1:2002-05-04 00\\:00-0500:","",1455036610861000],
["1:2002-05-04 00\\:00-0500:value","3.0",1455036610861000],
["1:2002-05-05 00\\:00-0500:","",1455036610861000],
["1:2002-05-05 00\\:00-0500:value","4.0",1455036610861000],
["1:2002-05-06 00\\:00-0500:","",1455036610861000],
["1:2002-05-06 00\\:00-0500:value","5.0",1455036610861000],
["1:2002-05-07 00\\:00-0500:","",1455036610861000],
["1:2002-05-07 00\\:00-0500:value","6.0",1455036610861000],
["1:2002-05-08 00\\:00-0500:","",1455036610861000],
["1:2002-05-08 00\\:00-0500:value","7.0",1455036610861000],
["1:2002-05-09 00\\:00-0500:","",1455036610861000],
["1:2002-05-09 00\\:00-0500:value","8.0",1455036610861000],
["1:2002-05-10 00\\:00-0500:","",1455036610862000],
["1:2002-05-10 00\\:00-0500:value","9.0",1455036610862000]]}
]
{code}
Is there anything special to your environment?
> After bulk loading CQL query on timestamp column returns wrong result
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-10583
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10583
> Project: Cassandra
> Issue Type: Bug
> Environment: Windows 2008 R2, Java x64 1.8.0_60, CentOS 7, Java
> 1.8.0._65
> Reporter: Kai Wang
> Fix For: 2.1.x, 2.2.x, 3.x
>
>
> I have this table:
> {noformat}
> CREATE TABLE test (
> tag text,
> group int,
> timestamp timestamp,
> value double,
> PRIMARY KEY (tag, group, timestamp)
> ) WITH CLUSTERING ORDER BY (group ASC, timestamp DESC)
> {noformat}
> First I used CQLSSTableWriter to bulk load a bunch of sstables. Then I ran
> this query:
> {noformat}
> cqlsh> select * from test where tag = 'MSFT' and group = 1 and timestamp
> ='2004-12-15 16:00:00-0500';
> tag | group | timestamp | value
> ------+-------+--------------------------+-------
> MSFT | 1 | 2004-12-15 21:00:00+0000 | 27.11
> MSFT | 1 | 2004-12-16 21:00:00+0000 | 27.16
> MSFT | 1 | 2004-12-17 21:00:00+0000 | 26.96
> MSFT | 1 | 2004-12-20 21:00:00+0000 | 26.95
> MSFT | 1 | 2004-12-21 21:00:00+0000 | 27.07
> MSFT | 1 | 2004-12-22 21:00:00+0000 | 26.98
> MSFT | 1 | 2004-12-23 21:00:00+0000 | 27.01
> MSFT | 1 | 2004-12-27 21:00:00+0000 | 26.85
> MSFT | 1 | 2004-12-28 21:00:00+0000 | 26.95
> MSFT | 1 | 2004-12-29 21:00:00+0000 | 26.9
> MSFT | 1 | 2004-12-30 21:00:00+0000 | 26.76
> (11 rows)
> {noformat}
> The result is obviously wrong.
> If I run this query:
> {noformat}
> cqlsh> select * from test where tag = 'MSFT' and group = 1 and timestamp
> ='2004-12-16 16:00:00-0500';
> tag | group | timestamp | value
> -----+-------+-----------+-------
> (0 rows)
> {noformat}
> In DevCenter I tried to create a similar table and insert a few rows but
> couldn't reproduce this. This may have something to do with the bulk loading
> process. But still, the fact cqlsh returns data that doesn't match the query
> is concerning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
