[
https://issues.apache.org/jira/browse/CASSANDRA-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084454#comment-14084454
]
Sylvain Lebresne commented on CASSANDRA-6960:
---------------------------------------------
bq. do we do the same optimizations for reading the rows to check for the
columns as we would if the partition key were supplied?
We don't read full partitions (we only read what matches {{rate_plan_id=90 and
metric_name='minutesOfUse' and extraction_date >= '2014-03-05' and
extraction_date <= '2014-03-05' }} for each partition) if that's what you're
asking for.
> Cassandra requires ALLOW FILTERING for a range scan
> ---------------------------------------------------
>
> Key: CASSANDRA-6960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6960
> Project: Cassandra
> Issue Type: Bug
> Reporter: J.B. Langston
>
> Given this table definition:
> {code}
> CREATE TABLE metric_log_a (
> destination_id text,
> rate_plan_id int,
> metric_name text,
> extraction_date 'org.apache.cassandra.db.marshal.TimestampType',
> metric_value text,
> PRIMARY KEY (destination_id, rate_plan_id, metric_name, extraction_date)
> );
> {code}
> It seems that Cassandra should be able to perform the following query without
> ALLOW FILTERING:
> {code}
> select destination_id, rate_plan_id, metric_name, extraction_date,
> metric_value
> from metric_log_a
> where token(destination_id) > ?
> and token(destination_id) <= ?
> and rate_plan_id=90
> and metric_name='minutesOfUse'
> and extraction_date >= '2014-03-05'
> and extraction_date <= '2014-03-05'
> allow filtering;
> {code}
> However, it will refuse to run unless ALLOW FILTERING is specified.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
