Have you tried tracing (TRACING ON) the query? That would usually give you
clues as to where it's failing. Cheers!
On Wed, Aug 16, 2017 at 12:03 AM, Vladimir Yudovin
wrote:
> Hi,
>
> I recently encountered with strange issue.
> Assuming there is table
>
> id PRIMARY KEY
> indexed text
> column t
SASI is in early experiment and had many major problems. for example,
"nodetool repair breaks SASI index"
https://issues.apache.org/jira/browse/CASSANDRA-13403
"OOM when using SASI index"
https://issues.apache.org/jira/browse/CASSANDRA-12662
I would not use SASI index for production.
Fay
On T
Hi,
I recently encountered with strange issue.
Assuming there is table
id PRIMARY KEY
indexed text
column text
CREATE custom index on table(indexed) using '...SASIIndex'
I inserted row like id=0, indexed='string1', column='just string'
When I did SELECT * FROM table WHERE id=0 AND
