[
https://issues.apache.org/jira/browse/CASSANDRA-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645563#comment-13645563
]
Jonathan Ellis commented on CASSANDRA-5514:
-------------------------------------------
I made a good point in 3581 that I forgot about. :)
Currently we only promote row tombstones if there is enough data in the row to
be worth indexing, under the reasoning that if it's not worth indexing we might
as well read the tombstone from the data file as well as any columns involved.
So, we'll need to change that to always promote (CASSANDRA-5526). As it
happens, I wrote this code once already for CASSANDRA-5487, so I'll see about
dusting it off.
> 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
