You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/07/19 01:04:07 UTC
[jira] [Commented] (CASSANDRA-7574) Support Custom Predicate in
CQL SELECT for Custom Secondary Index
[ https://issues.apache.org/jira/browse/CASSANDRA-7574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067060#comment-14067060 ]
Jonathan Ellis commented on CASSANDRA-7574:
-------------------------------------------
I'm not sure what problem you're trying to solve here, but adding a hardcoded pseudo-column that gets special treatment is not a good solution.
> Support Custom Predicate in CQL SELECT for Custom Secondary Index
> ------------------------------------------------------------------
>
> Key: CASSANDRA-7574
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7574
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Yeshvanthni
> Priority: Minor
>
> The SELECT query validation limits the predicates the custom secondary index can support.
> Possible Approaches:
> -Introduction of a special predicate string like custom_predicate which by-passes validation
> CREATE CUSTOM INDEX ON table(column) USING 'org.example.CustomSecondaryIndex';
> Select * from table where custom_predicate=" something_only_custom_class_understands"
> This might open up possibilities like,
> - Range queries on secondary indexed columns etc
> - Wild cards
--
This message was sent by Atlassian JIRA
(v6.2#6252)