Hi, I am trying to understand whether it is possible to set an expiry time at a key-value level instead of the cache level.
>From my understanding, 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. I would like to know if there is a way for only a specific key-value pairs in the cache to override the default expiry time at the time of putting the key-value from a thin client. By reading up the docs of the thin clients ( https://apacheignite.readme.io/docs/java-thin-client-key-value ), I am inferring that there is no method signature that accepts expiry time for put operation. So, I would like to confirm this behavior and interested in knowing if anyone had this kind of use case or perhaps a feature request. Thanks in advance! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
