cassandra-commits mailing list archives

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


Jonathan Ellis commented on CASSANDRA-3078:

bq. I don't follow.

I'm making an educated guess here, but it looks to me like Ed saw my comment about using the
hashconstruct for strategy_options and other Maps in Thrift and thought we were breaking backwards
compatibility there, which is not the case.

bq. squeezing new features in through loopholes in the current api.

That's not what this is about.  We're not trying to let old clients use new features that
didn't exist then, we just need to allow old clients to continue to operate with their old
feature set (i.e., use index_type=KEYS to denote "I want this column indexed.")

bq. the project is too young IMO to [care about humoring old clients]

It has nothing to do with age or version number and everything to do with user base.  We made
the call to break API compatibility between 0.6 and 0.7 as a one-time thing, but we've been
very clear that we'll do everything we can to not do that again.  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.

> 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