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/02/14 15:21:23 UTC

[jira] [Updated] (CASSANDRA-5514) Track min/max clustered values per sstable to optimize reads

     [ https://issues.apache.org/jira/browse/CASSANDRA-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-5514:
--------------------------------------

    Summary: Track min/max clustered values per sstable to optimize reads  (was: Allow timestamp hints)

> Track min/max clustered values per sstable to optimize reads
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-5514
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5514
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>            Assignee: Marcus Eriksson
>             Fix For: 2.0 beta 1
>
>         Attachments: 0001-CASSANDRA-5514-v1.patch, 0001-CASSANDRA-5514-v2.patch
>
>
> Slice queries can't optimize based on timestamp except for rare cases (CASSANDRA-4116).  However, many common queries involve an implicit time component, where the application author knows that he is only interested in data more recent than X, or older than Y.
> We could use the per-sstable max and min timestamps we track to avoid touching cold data if we could pass a hint to Cassandra about the time range we care about.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)