cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3078) Make Secondary Indexes Pluggable
Date Fri, 26 Aug 2011 21:31:29 GMT


Edward Capriolo commented on CASSANDRA-3078:

Currently, the generated thrift for lists StrategyOptions as type Map<String,String>.
After the 0.6.X->0.7.X supposedly the thrift API was solidified. Maybe these structures
should be yaml/json encoded into strings? I know that pluggable 2X indexes are going to be
fun, but if we get creative we do not have to change the interface that everyone describes
as "stabilized".  (Just playing devils advocate here) (Sorry jake)

> 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