[
https://issues.apache.org/jira/browse/GEODE-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16344131#comment-16344131
]
Jinmei Liao commented on GEODE-3876:
------------------------------------
Seems like there are two apis on RegionFactory related to CustomExpiry:
{code}
public RegionFactory<K, V> setCustomEntryIdleTimeout(CustomExpiry<K, V> custom)
public RegionFactory<K, V> setCustomEntryTimeToLive(CustomExpiry<K, V> custom)
{code}
so, user can specify either one of them?
> gfsh command for custom expiry
> ------------------------------
>
> Key: GEODE-3876
> URL: https://issues.apache.org/jira/browse/GEODE-3876
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
> Reporter: Swapnil Bawaskar
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When creating or altering a region the ability to add custom expiration is
> missing.
> It would be great to have something like this:
> {code}
> alter/create region --name=regioName
> [--region-custom-expiry=customExpiryImplementationClassName]
> {code}
> If the class implementing custom expiry also implements Declarable, we should
> add support for passing parameters to the init method.
>
> {code}
> alter/create region --name=regionName
> --region-custom-expiry=CustomExpirayImplementation?{'k':'v','k2':'v2'}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)