Vishnu Bharathi created IGNITE-12731:
----------------------------------------
Summary: Support expiry policy at a key value level for the thin
clients
Key: IGNITE-12731
URL: https://issues.apache.org/jira/browse/IGNITE-12731
Project: Ignite
Issue Type: Improvement
Reporter: Vishnu Bharathi
Apache Ignite supports expiry policies at a cache
level ( [https://apacheignite.readme.io/docs/expiry-policies] ), so that all
the key-value pairs in the cache gets expired at a specific time. When asked if
there is a way to set expiry policy at a key value level in the user mailing
list (
[http://apache-ignite-users.70518.x6.nabble.com/Expiry-policy-at-a-key-value-level-td31568.html]
) got the below response
|Hello,
IgniteCache has a way to specify the expiry policy at key level for thick
clients via IgniteCache#withExpiryPolicy() facade. I think it may be reasonable
to add similar option to the thin clients protocol as well. Feel free to open a
ticket.|
Will it be ok to add this functionality to the core project?
To start with, I would like to know what components are involved in-order to
make this change. Is it just the thin client code or any other components are
also involved?
Would be greatly helpful, if someone could point me to the source files, code
paths etc. for implementing this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
