[
https://issues.apache.org/jira/browse/CASSANDRA-7574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074618#comment-14074618
]
Yeshvanthni commented on CASSANDRA-7574:
----------------------------------------
for example,Even If the Custom Secondary Index is capable of handling say range
queries like,
select * from tweet where tweettimepoc>xx and tweettimepoc<xxx
The CQL syntax validator invalidates the above query as range query is not
allowed on this column type although it does have a secondary index configured
which is capable of handling it.
One way to workaround this is to introduce a custom_predicate text column as an
addition to the existing table.This predicate is parsed internally by the
Custom Secondary Index for such special queries. This improvement is a nice to
have to avoid such hacks and that is why its prioritized as minor
> 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)
