Hi, Yes, every cache request has Flags byte right after cacheId. There is FLAG_WITH_EXPIRY_POLICY = 0x04. When this flag is set, server expects 3 long values (3x8 bytes) after flags byte, representing TTL for Create, Update, and Access, in milliseconds
For example, if we want to store a cache entry that should expire in 3 seconds, we execute OP_CACHE_PUT (1001) operation, set FLAG_WITH_EXPIRY_POLICY, and pass 3000, 0, 0 as TTL values. Let me know if you need more details. Thanks, Pavel On Tue, May 19, 2020 at 3:27 PM scriptnull <vishnubharath...@gmail.com> wrote: > Hi, > > I am referring to any of the thin clients > (java/.net/c++/node.js/python/php) > documented at https://apacheignite.readme.io/docs/thin-clients > > I wonder if any of those thin clients have an API to set TTL for a > key-value > in a cache. If so I can reverse engineer the implementation of it and > implement it in the ruby thin client implementation that I am currently > working on. > > More specifically, I am interested in knowing if there is an operation in > binary protocol like OP_CACHE_UPDATE_TTL > > If there is such an operation, I could call it via a ruby thin client > implementation that I am working on currently. > > Regards, > Vishnu Bharathi P > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
