cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3078) Make Secondary Indexes Pluggable
Date Sat, 27 Aug 2011 11:14:37 GMT


T Jake Luciani commented on CASSANDRA-3078:

bq. Otherwise you're essentially forced to take downtime to upgrade your app at the same time
as your database, and that's not acceptable for almost all our users.

My concern is confusion around multiple ways of creating indexes long-term.  So perhaps we
try to utilize index_type so it keeps being "the way" to index columns.  One idea is we remove
index_class add a CUSTOM index_type, that would require specifying the classname as a index_option.

   index_type: CUSTOM
   index_options: {
         class_name: o.a.c.d.MyIndexType

> Make Secondary Indexes Pluggable 
> ---------------------------------
>                 Key: CASSANDRA-3078
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>              Labels: secondary_index
>             Fix For: 1.0
>         Attachments: v1-0001-CASSANDRA-3078-pluggable-secondary-indexes.txt, v1-0002-CASSANDRA-3078-pluggable-secondary-index-thrift.txt
> CASSANDRA-2982 got us most of the way there...
> This ticket removes the IndexType enum (while keeping support for KEYS internally from
old cf metadata).
> You now specify a index_class rather than index_type.  index_class is the full classname
of the SecondaryIndex impl.  This also adds a index_options map to pass extra info to the
secondary index impl if needed.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message