[
https://issues.apache.org/jira/browse/CASSANDRA-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645010#comment-13645010
]
Tupshin Harper edited comment on CASSANDRA-5514 at 4/30/13 12:06 PM:
---------------------------------------------------------------------
See CASSANDRA-3581 for a previous ticket along similar lines.
+1 on no additional syntax and Sylvain's general approach.
+1000 on a time-series aware compaction strategy. That is where the big win
will be.
was (Author: tupshin):
See CASSANDRA-5518 for a previous ticket along similar lines.
+1 on no additional syntax and Sylvain's general approach.
+1000 on a time-series aware compaction strategy. That is where the big win
will be.
> 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
