Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 12 Sep 2013 18:15:53 +0000 (UTC)
From: "Oleg Kibirev (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12667676.1378763111935.124246.1379009753791@arcas>
In-Reply-To: <JIRA.12667676.1378763111935@arcas>
References: <JIRA.12667676.1378763111935@arcas>
Subject: [jira] [Commented] (CASSANDRA-5988) Make hint TTL customizable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765724#comment-13765724 ] 

Oleg Kibirev commented on CASSANDRA-5988:
-----------------------------------------

That would be ideal, yes. 
                
> Make hint TTL customizable
> --------------------------
>
>                 Key: CASSANDRA-5988
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5988
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Oleg Kibirev
>
> Currently time to live for stored hints is hardcoded to be gc_grace_seconds. This causes problems for applications using backdated deletes as a form of optimistic locking. Hints for updates made to the same data on which delete was attempted can persist for days, making it impossible to determine if delete succeeded by doing read(ALL) after a reasonable delay. We need a way to explicitly configure hint TTL, either through schema parameter or through a yaml file.

--
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