You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Kukushkin (Jira)" <ji...@apache.org> on 2022/05/12 10:36:00 UTC

[jira] [Updated] (IGNITE-14326) Resetting Ignite cache entry TTL

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

Alexey Kukushkin updated IGNITE-14326:
--------------------------------------
    Summary: Resetting Ignite cache entry TTL  (was: Add CacheEntry#setTtl method)

> Resetting Ignite cache entry TTL
> --------------------------------
>
>                 Key: IGNITE-14326
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14326
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.3
>            Reporter: Stephen Darlington
>            Assignee: Stephen Darlington
>            Priority: Major
>              Labels: cggg
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Ignite provides a way to specify an expiry policy on per entry level, but there is no way to know the current TTL for a particular key or refresh the TTL without first retrieving the record.
> Ticket IGNITE-7641 details the IgniteCache#ttl() method. This ticket is about _setting_ the TTL.
> The API for this is less well defined than the get TTL method. Suggest a number of options:
>  * Update using the default TTL policy
>  * Update using a specified long
>  * Update using a specified Expiry policy



--
This message was sent by Atlassian Jira
(v8.20.7#820007)