cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11182) Enable SASI index for collections
Date Thu, 09 Jun 2016 00:45:21 GMT

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

Pavel Yaskevich commented on CASSANDRA-11182:
---------------------------------------------

I agree with [~beobal] on that, effectively the most important thing we need to enable indexing
for collections and partition keys is TokenTree which accepts variable size keys (such would
enable different parititoners, collections support, primary key indexing etc.), once that's
done all of the changes are going to be pretty straight-forward.

> Enable SASI index for collections
> ---------------------------------
>
>                 Key: CASSANDRA-11182
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11182
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: DOAN DuyHai
>            Assignee: Alex Petrov
>            Priority: Minor
>
> This is a follow up ticket for post Cassandra 3.4 SASI integration.
> Right now it is possible with standard Cassandra 2nd index to:
> 1. index list and set elements ( {{WHERE list CONTAINS xxx}})
> 2. index map keys ( {{WHERE map CONTAINS KEYS 'abc'}} )
> 3. index map entries ( {{WHERE map\['key'\]=value}})
>  It would be nice to enable these features in SASI too.
>  With regard to tokenizing, we might want to allow wildcards ({{%}}) with the CONTAINS
syntax as well as with index map entries. Ex:
> * {{WHERE list CONTAINS 'John%'}}
> * {{WHERE map CONTAINS KEY '%an%'}}
> * {{WHERE map\['key'\] LIKE '%val%'}}
> /cc [~xedin] [~rustyrazorblade] [~jkrupan]



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

Mime
View raw message