[
https://issues.apache.org/jira/browse/CASSANDRA-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078599#comment-14078599
]
Rustam Aliyev edited comment on CASSANDRA-7637 at 7/29/14 11:47 PM:
--------------------------------------------------------------------
Agree, LIKE would be more SQL compatible way to do it. It will be very limited
functionality for LIKE, only {{%}} wildcard in the end of an expression. But I
think it's still better.
Regarding wildcards, if we try maximize SQL compatibility, I'd choose {{%}}
instead of {{*}}.
I'm also removing inet type - I think there are better ways to do range queries
on that one.
was (Author: rstml):
Agree, LIKE would be more SQL compatible way to do it. It will be very limited
functionality for LIKE, only {{%}} wildcard in the end of an expression. But I
think it's still better.
I'm also removing inet type - I think there are better ways to do range queries
on that one.
Btw, in your example above it should be {{%}} in the end.
> Add CQL3 keyword for efficient lexical range queries (e.g. START_WITH)
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-7637
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7637
> Project: Cassandra
> Issue Type: New Feature
> Components: API
> Reporter: Rustam Aliyev
> Fix For: 3.0
>
>
> Currently, if I want to perform range query on lexical type I need to do
> something like this:
> {code}
> SELECT * FROM profile WHERE profile_id = 123 AND
> attribute > 'interests.food.' AND
> attribute < 'interests.food.z';
> {code}
> This is very efficient range query. Yet, many users who are not familiar with
> Thrift and storage level implementation are unaware of this "trick".
> Therefore, it would be convenient to introduce CQL keyword which will do this
> more simply:
> {code}
> SELECT * FROM profile WHERE profile_id = 123 AND
> attribute START_WITH('interests.food.');
> {code}
> Keyword would have same restrictions as other inequality search operators
> plus some type restrictions.
> Allowed types would be:
> * {{ascii}}
> * {{text}} / {{varchar}}
> * {{map<text, *>}} (same for ascii) (?)
> * {{set<text>}} (same for ascii) (?)
> (?) may require more work, therefore optional
--
This message was sent by Atlassian JIRA
(v6.2#6252)
