[
https://issues.apache.org/jira/browse/IGNITE-14326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570077#comment-17570077
]
Alexander Lapin edited comment on IGNITE-14326 at 7/22/22 3:34 PM:
-------------------------------------------------------------------
[~kukushal]
Hi!
First of all seems that IGNITE-7641 isn't actually a duplicate of given one
because it's about retrieving ttl and IGNITE-14326 is about resetting.
Besides that it's not quite clear whether it's required to reset only accessTtl
or both accessTtl and createTtl.
Could you please provide more information?
was (Author: alapin):
[~cyberdemn]
Hi!
First of all seems that IGNITE-7641 isn't actually a duplicate of given one
because it's about retrieving ttl and IGNITE-14326 is about resetting.
Besides that it's not quite clear whether it's required to reset only accessTtl
or both accessTtl and createTtl.
Could you please provide more information?
> 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
> Priority: Major
> Labels: cggg
> Original Estimate: 64h
> Remaining Estimate: 64h
>
> Ignite provides a way to specify an expiry policy on per entry level, but
> there is no way to refresh the TTL without first retrieving the record, which
> is slow and resource consuming if an entry is large.
> Provide a method to reset Ignite cache entry TTL.
> Suggested API (to be discussed with community):
> {{IgniteCache#touch(key)}}: resets the TTL using the latest TTL value or does
> nothing if no TTL was specified for the key.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
