[CASSANDRA-13478] SASI Sparse mode overflow corrupts the SSTable

• Type: Bug
• Status: Open
• Priority: Low
• Resolution: Unresolved
• Component/s: Feature/SASI

Environment

cqlsh 5.0.1 | Cassandra 3.10 | CQL spec 3.4.4 | Native protocol v4 | ubuntu 14.04

• Severity: Low
• Since Version: 3.10
• Assignee: Alex Petrov
• Reporter: jack chen

Authors

Alex Petrov

• Created: 26/Apr/17 08:39
• Updated: 27/Nov/19 18:04

Description

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:

CREATE TABLE XXX.userlist (
    userid text PRIMARY KEY,
    lastposttime timestamp
)
Select * from userlist where lastposttime> '2017-04-01 16:00:00+0000';

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

Issue Links

• is duplicated by: CASSANDRA-15082 SASI SPARSE mode 5 limit