[
https://issues.apache.org/jira/browse/CASSANDRA-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646244#comment-13646244
]
Aleksey Yeschenko commented on CASSANDRA-5484:
----------------------------------------------
I was going for
{noformat}
CREATE INDEX ON <table>(<column) WITH type = CUSTOM AND options =
{'class_name': 'MyCostomIndex', ...};
{noformat}
to allow parametrization for KEYS/COMPOSITES index in the future, but I can't
think of what we could actually want to parametrize with them, so scratch that.
Let's only leave parametrization for CUSTOM.
But for the sake of consistency with CREATE KEYSPACE and
compaction,compression,etc. options for CREATE TABLE, I'd like options to be a
map (and replace 'class_name' key with 'class' internally, also for
consistency), e.g.
{noformat}
CREATE INDEX ON <table>(<column>) WITH options = {'class':
'MyCustomIndex',...};
{noformat}
Not sure about CREATE CUSTOM INDEX vs. just treating CREATE INDEX with non-null
options as custom, implicitly. I believe that every time we add a keyword to
CQL, even an unreserved one, a kitten dies somewhere, so I'd like to avoid
doing that.
> Support custom secondary indexes in CQL
> ---------------------------------------
>
> Key: CASSANDRA-5484
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5484
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.4
> Reporter: Benjamin Coverston
> Assignee: Aleksey Yeschenko
>
> Through thrift users can add custom secondary indexes to the column metadata.
> The following syntax is used in PLSQL, and I think we could use something
> similar.
> CREATE INDEX <NAME> ON <TABLE> (<COLUMN>) [INDEXTYPE IS (<TYPENAME>)
> [PARAMETERS (<PARAM>[, <PARAM>])]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
