[ https://issues.apache.org/jira/browse/CASSANDRA-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666231#comment-13666231 ]
Sylvain Lebresne commented on CASSANDRA-5514: --------------------------------------------- bq. regarding DCT I haven't looked at the patch details, but my intuition would be do handle DCT as any non-composite type. That's what CQL3 does really. > 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, > 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 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