[
https://issues.apache.org/jira/browse/CASSANDRA-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-5514:
---------------------------------------
Attachment: 0001-CASSANDRA-5514-v1.patch
* tracks min/max column names in sstables (according to comparator)
* uses the min/max column names no eliminate sstables during slices (and
maxLocalDeletionTime to figure out if an sstable has a tombstone)
[~jbellis] - i have not made SSTM.Collector cql-aware, i couldnt really see a
reason for it, could you elaborate on that comment? We should be able to
eliminate sstables based on the entire column name, even if it is a composite
one right?
> 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
>
> Attachments: 0001-CASSANDRA-5514-v1.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 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
