cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan West (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11434) Support EQ/PREFIX queries in CONTAINS mode without tokenization by augmenting SA metadata per term
Date Mon, 28 Mar 2016 23:16:25 GMT

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

Jordan West commented on CASSANDRA-11434:
-----------------------------------------

The branch linked below implements the described changes. The test changes reflect the feature
changes made. This is a backwards compatible change. It uses an unused (zeroed) byte in the
index header to indicate if the index supports the new kind of query. Existing indexes will
automatically be upgraded to support marked partials when compacted. PREFIX queries against
a CONTAINS column whose indexes have not yet been upgraded will still result in an exception
and failed request (but with a different exception than {{InvalidRequestException}}). Once
the index is rebuilt (manually or via compaction) the exception will stop being thrown. 

||branch||testall||dtest||
|[CASSANDRA-11434|https://github.com/xedin/cassandra/tree/CASSANDRA-11434]|[testall|http://cassci.datastax.com/job/xedin-CASSANDRA-11434-testall/]|[dtest|http://cassci.datastax.com/job/xedin-CASSANDRA-11434-dtest/]|

> Support EQ/PREFIX queries in CONTAINS mode without tokenization by augmenting SA metadata
per term
> --------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11434
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11434
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: sasi
>            Reporter: Pavel Yaskevich
>            Assignee: Jordan West
>             Fix For: 3.6
>
>
> We can support EQ/PREFIX requests to CONTAINS indexes by tracking "partiality" of the
data stored in the OnDiskIndex and IndexMemtable, if we know exactly if current match represents
part of the term or it's original form it would be trivial to support EQ/PREFIX since PREFIX
is subset of SUFFIX matches.
> Since we attach uint16 size to each term stored we can take advantage of sign bit so
size of the index is not impacted at all.



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

Mime
View raw message