[
https://issues.apache.org/jira/browse/CASSANDRA-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641939#comment-13641939
]
Jonathan Ellis commented on CASSANDRA-5514:
-------------------------------------------
Sylvain suggests that instead of adding extra syntax, we track min and max
column values (cell name components) on a per-sstable basis. This requires
less moving pieces to implement (don't need to touch QueryProcessor) and I'm
generally a fan of less special cases.
A small downside is that we'll need to make SSTableMetadata.Collector
cql-aware. Simplest approach IMO is to just track all the "clustering"
components per-sstable, it's not going to be a whole lot of extra data consumed.
> Allow timestamp hints
> ---------------------
>
> 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
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
