DOAN DuyHai created CASSANDRA-11132:
---------------------------------------

             Summary: [SASI Pre-QA] Creating SPARSE index with non literal type 
leaves the index in a stalled state
                 Key: CASSANDRA-11132
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11132
             Project: Cassandra
          Issue Type: Bug
          Components: CQL
         Environment: Tested from build 
[CASSANDRA-11067|https://issues.apache.org/jira/browse/CASSANDRA-11067]
            Reporter: DOAN DuyHai


Tested from build 
[CASSANDRA-11067|https://issues.apache.org/jira/browse/CASSANDRA-11067]

{code:sql}
CREATE KEYSPACE music WITH replication = {'class': 'SimpleStrategy', 
'replication_factor': '1'}  AND durable_writes = true;

CREATE TABLE music.albums (
    id int PRIMARY KEY,
    artist text,
    title text
);

CREATE CUSTOM INDEX ON music.albums (title) USING 
'org.apache.cassandra.index.sasi.SASIIndex' WITH OPTIONS = {'mode': 'SPARSE'};

ServerError: <ErrorMessage code=0000 [Server error] 
message="java.lang.RuntimeException: java.util.concurrent.ExecutionException: 
java.lang.RuntimeException:   java.lang.reflect.InvocationTargetException">

{code}

The real exception message in _/var/log/cassandra/system.log_ is : *Caused by: 
java.lang.IllegalStateException: Unsupported mode: SPARSE.*

Worst, the index is created but not visible when calling *DESCRIBE TABLE 
albums;*. It is visible though in the *system_keyspace.indexs* table.

Any further attempt to create a correct index on the same column fails:

{code:sql}
CREATE CUSTOM INDEX ON music.albums (title) USING 
'org.apache.cassandra.index.sasi.SASIIndex' WITH OPTIONS = {'mode': 'PREFIX', 
'analyzer_class': 
'org.apache.cassandra.index.sasi.analyzer.NonTokenizingAnalyzer', 
'case_sensitive': 'false'};

InvalidRequest: code=2200 [Invalid query] message="Index albums_title_idx 
already exists"

{code}

We need to drop the invisible index before being able to create another index 
on the same column




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to