[
https://issues.apache.org/jira/browse/IGNITE-22189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Davydov updated IGNITE-22189:
------------------------------------
Description:
The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
string representation, which at this point is a simple className +@ + hashCode
in hex, that is default {{Object#toString()}} behaviour. This is not
informative for an end user of the API.
In addition, it is useful to have information about existing cache entries that
are about to expire (eligible for cache expiry policy).
{*}TODO{*}:
* To make the {{CacheView#expiryPolicyFactory}} method return readable,
human-oriented output, one should refactor the method or
{{Factory<ExpiryPolicy>}} child classes to provide the cache expiry policy
setting in readable form with policy type and ttl.
* Within the cache group view ({{{}CacheGroupView{}}}), check the entries
presence eligible for expiry policy. It can be done with O(1) time complexity
for in-memory, and O(number of partitions) for persistent mode.
* Within the cache view ({{{}CacheView{}}}), check the entries presence
eligible for expiry policy. It can be done with O(logN) time complexity for
in-memory, and O(number of partitions) for persistent mode.
was:
The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
string representation, which at this point is a simple className +@ + hashCode
in hex, that is default {{Object#toString()}} behaviour. This is not
informative for an end user of the API.
In addition, it is useful to have information about existing cache entries that
are about to expire (eligible for cache expiry policy).
{*}TODO{*}:
* To make the {{CacheView#expiryPolicyFactory}} method return readable,
human-oriented output, one should refactor the method or
{{Factory<ExpiryPolicy>}} child classes to provide the cache expiry policy
setting in readable form with policy type and ttl.
* Within the cache group view ({{CacheGroupView}}), check the entries presence
eligible for expiry policy. It can be done with O(1) time complexity for
in-memory, and O(number of partitions) for persistent mode.
> Display Expiry Policy information in the system view
> ----------------------------------------------------
>
> Key: IGNITE-22189
> URL: https://issues.apache.org/jira/browse/IGNITE-22189
> Project: Ignite
> Issue Type: Improvement
> Reporter: Maksim Davydov
> Assignee: Maksim Davydov
> Priority: Minor
> Labels: ise
>
> The {{CacheView#expiryPolicyFactory}} method returns the ExpiryPolicyFactory
> string representation, which at this point is a simple className +@ +
> hashCode in hex, that is default {{Object#toString()}} behaviour. This is not
> informative for an end user of the API.
> In addition, it is useful to have information about existing cache entries
> that are about to expire (eligible for cache expiry policy).
> {*}TODO{*}:
> * To make the {{CacheView#expiryPolicyFactory}} method return readable,
> human-oriented output, one should refactor the method or
> {{Factory<ExpiryPolicy>}} child classes to provide the cache expiry policy
> setting in readable form with policy type and ttl.
> * Within the cache group view ({{{}CacheGroupView{}}}), check the entries
> presence eligible for expiry policy. It can be done with O(1) time complexity
> for in-memory, and O(number of partitions) for persistent mode.
> * Within the cache view ({{{}CacheView{}}}), check the entries presence
> eligible for expiry policy. It can be done with O(logN) time complexity for
> in-memory, and O(number of partitions) for persistent mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
