[
https://issues.apache.org/jira/browse/CASSANDRA-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092133#comment-13092133
]
T Jake Luciani commented on CASSANDRA-3078:
-------------------------------------------
bq. I don't see any changes to strategy options in Thrift. The hashconstruct
from CASSANDRA-3081 only affects how the cli parses it.
I don't follow. There are new fields in CfDef thrift struct which are picked
up by ColumnDefinition.
bq. this does break compatibility for clients using IndexType instead of a
class name. We should leave both the old Type optional field, as well as the
new one, and provide backwards compatibility for clients specifying Type.
I can do this but it seems like it only needs to support compatibility in the
system table structs (which it does). Would we remove this after 1.0?
> Make Secondary Indexes Pluggable
> ---------------------------------
>
> Key: CASSANDRA-3078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3078
> 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: http://www.atlassian.com/software/jira
