For the record, we've found the issue, it is not related to SASI, the
inconsistencies are due to inconsistent data, need a good repair to put
them back in sync.
Using QUORUM CL grant consistent results when querying
On Fri, Aug 5, 2016 at 1:18 PM, George Webster wrote:
> Thanks DuyHai,
>
> I wo
Thanks DuyHai,
I would agree but we have not performed any delete operations in over a
month. To me this looks like a potential bug or misconfiguration (on my
end) with SASI.
I say this for a few reasons:
1) we have not performed a delete operation since the indexes were created
2) when I perform
Ok the fact that you see some rows and after a while you see 0 rows means
that those rows are deleted.
Since SASI does only index INSERT & UPDATE but not DELETE, management of
tombstones is let to Cassandra to handle.
It means that if you do an INSERT, you'll have an entry into SASI index
file bu
The indexes were written about 1-2 months ago. No data has been added to
the servers since the indexes were created. Additionally, the indexes
appeared to be stable until I noticed the issue today. ... which occurred
after a made a large query without setting a LIMIT
I set the consistency level an
One possible explanation is that you're querying data while the index files
are being built so that the result are different
The second possible explanation is the consistency level.
Try the query again using CL = QUORUM, try on several nodes to see if the
results are different
On Tue, Aug 2, 20
Hey DuyHai,
Thank you for your help.
1) Cassandra version
[cqlsh 5.0.1 | Cassandra 3.5 | CQL spec 3.4.0 | Native protocol v4]
2) CREATE CUSTOM INDEX statement for your index
CREATE CUSTOM INDEX objects_mime_idx ON test.objects (mime) USING
'org.apache.cassandra.index.sasi.SASIIndex' WITH OPTION
Hello George
Can you provide more details ?
1) Cassandra version
2) CREATE CUSTOM INDEX statement for your index
3) Consistency level used for your SELECT
4) Replication factor
5) Are you creating the index when the table is EMPTY or have you created
the index when the table already contains some
Hey guys and gals,
I am having a strange issue with Cassandra SASI and I was hoping you could
help solve the mystery. My issue is inconsistency between returned results
and strange log errors.
The biggest issue is that when I perform a query I am getting back
inconsistent results. First few times
