Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 21 May 2013 03:51:19 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12644620.1366904754452.350948.1369108279871@arcas>
In-Reply-To: <JIRA.12644620.1366904754452@arcas>
References: <JIRA.12644620.1366904754452@arcas>
Subject: [jira] [Updated] (CASSANDRA-5514) Allow timestamp hints
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-5514:
--------------------------------------

    Reviewer: slebresne
    
> 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