[
https://issues.apache.org/jira/browse/CASSANDRA-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000417#comment-16000417
]
Alex Petrov commented on CASSANDRA-13478:
-----------------------------------------
Could you please explain why you think this is related to the TTL? I've tried
it locally and query by the timestamp field works fine with/without flush,
with/without restart. There's no default TTL on the table, do you maybe use the
TTL on insert? Could you paste a complete example to reproduce it maybe?
> SASIndex has a time to live issue in Cassandra
> ----------------------------------------------
>
> Key: CASSANDRA-13478
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13478
> Project: Cassandra
> Issue Type: Bug
> Components: sasi
> Environment: cqlsh 5.0.1 | Cassandra 3.10 | CQL spec 3.4.4 | Native
> protocol v4 | ubuntu 14.04
> Reporter: jack chen
> Assignee: Alex Petrov
> Priority: Minor
> Attachments: schema
>
>
> I have a table, the schema can be seen in attach file
> I would like to search the data using the timestamp data type with lt gt eq
> as a query condition,
> Ex:
> {code}
> CREATE TABLE XXX.userlist (
> userid text PRIMARY KEY,
> lastposttime timestamp
> )
> Select * from userlist where lastposttime> '2017-04-01 16:00:00+0000';
> {code}
> There are 2 conditions :
> If I insert the data and then select it, the result will be correct
> But in case I insert data and then the next day I restart Cassandra, and
> after that select the data, there will be no data selected
> The difference is that there is no Service restart on th next day in the
> first manner. Actually, the data are still living in Cassandra, but TimeStamp
> can’t be used as the query condition
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
