[
https://issues.apache.org/jira/browse/CASSANDRA-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637918#comment-13637918
]
Sylvain Lebresne commented on CASSANDRA-5484:
---------------------------------------------
bq. Let's also split out parameterization to another ticket – I don't think we
support that yet for any index type.
Actually, I think we do need it here because that's the way we pass the class
name for CUSTOM indexes. So I think this could look like:
{noformat}
CREATE CUSTOM INDEX ON <table>(<column>) WITH class='MyCustomIndex';
{noformat}
(I do note that thrift uses 'class_name' in the index options, but for CQL3,
using just 'class' would be somewhat more coherent with the compaction strategy.
I will also note that on the thrift side, we have 3 different IndexType: Keys,
Composites and Custom. But for CQL3, I am not convinced that making the
different between Keys and Composites is a good idea: CQL3 knows enough about
the tables to know with one to use. In other words, I think the only <method>
we should support here is 'CUSTOM' (or nothing).
And while in theory it is possible to create a KEYS index on a composite table
on the thrift side, it's unclear whether it is useful or not for CQL3 and
should be supported. So even if we do want to consider it, then I think that
this part should be split to a separate ticket.
> 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
