cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrés de la Peña (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6480) Custom secondary index options in CQL3
Date Fri, 13 Dec 2013 10:46:09 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847379#comment-13847379
] 

Andrés de la Peña commented on CASSANDRA-6480:
----------------------------------------------

Hi Sylvain,
yes, we have an use case. We're developing a custom secondary index based on Lucene, it would
be nice to able to have a syntax similar to the 'create keyspace' statement, in which we can
pass the complete index options map (which already exists in the code). For example:

CREATE TABLE documents (
  key timeuuid,
  date timestamp,
  spanish_text varchar,
  english_text varchar,
  PRIMARY KEY key);

CREATE CUSTOM INDEX ON demo.users (spanish_text) USING {'class' : 'org.stratio.FullTextIndex',
'analyzer': 'SpanishAnalyzer', 'storage':'/mnt/ssd/indexes/'};
CREATE CUSTOM INDEX ON demo.users (english_text) USING {'class' : 'org.stratio.FullTextIndex',
'analyzer': 'EnglishAnalyzer', 'storage':'/mnt/ssd/indexes/'};

> Custom secondary index options in CQL3
> --------------------------------------
>
>                 Key: CASSANDRA-6480
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6480
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Andrés de la Peña
>              Labels: cql3, index
>
> The CQL3 "create index" statement syntax does not allow to specify the options map internally
used by custom indexes. 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message