[
https://issues.apache.org/jira/browse/CASSANDRA-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713620#comment-14713620
]
Sam Tunnicliffe commented on CASSANDRA-10124:
---------------------------------------------
bq. I'm not convinced that USING INDEX should automatically remove the need
for ALLOW FILTERING
That's why I added
bq. Perhaps the ALLOW FILTERING override could be dependent on all the
restrictions being able to besatisfied by the specified index
> Full support for multi-column and per-row indexes
> -------------------------------------------------
>
> Key: CASSANDRA-10124
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10124
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Labels: client-impacting
> Fix For: 3.0 beta 2
>
>
> Since CASSANDRA-6717 decoupled a secondary index from a single column, we can
> expand support for indexes with multiple target columns and for row-based
> indexes with truly dynamic targets.
> Much of the plumbing for this has been done in CASSANDRA-7771, CASSANDRA-6717
> & by the API rework in CASSANDRA-9459. What remains is:
> * Decide on syntax for DDL statements
> * Decide on WHERE clause syntax for SELECT (there is some discussion on this
> in the comments of CASSANDRA-9459)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
