> you could specify the expiration policy on the actual "Put" call itself That is true on the protocol level. User-facing API has WithExpiryPolicy so we don't have to add an additional overload for every cache operation.
On Tue, May 19, 2020 at 5:00 PM Marty Jones <[email protected]> wrote: > Pavel, > > My bad, I misunderstood the question. The code I am using works fine. I > thought the previous discussion was stating that you could specify the > expiration policy on the actual "Put" call itself. > > On Tue, May 19, 2020 at 8:53 AM Pavel Tupitsyn <[email protected]> > wrote: > >> Marty, can you please elaborate? >> We are talking about protocol-level details in this thread. >> Your code for .NET Thin Client seems to be fine, does it work as expected? >> >> On Tue, May 19, 2020 at 4:39 PM Marty Jones <[email protected]> >> wrote: >> >>> I am not seeing that option in the ASP.NET thin client. This is how I >>> accomplished setting an expiration policy: >>> >>> ICacheClient<string, CacheItemEntry> cache = >>> igniteClient.GetCache<string, CacheItemEntry>("testCache"); >>> >>> cache.WithExpiryPolicy(new ExpiryPolicy(TimeSpan.FromSeconds(15), null, >>> null)) >>> .Put("test1", new CacheItemEntry() { Entry = "test" }); >>> >>> On Tue, May 19, 2020 at 8:17 AM Pavel Tupitsyn <[email protected]> >>> wrote: >>> >>>> > if there is support for setting expire times for multiple key-values >>>> > while doing a OP_CACHE_PUT_ALL >>>> >>>> The answer is yes. All key-val operations support expiration, namely: >>>> OP_CACHE_PUT >>>> OP_CACHE_PUT_IF_ABSENT >>>> OP_CACHE_PUT_ALL >>>> OP_CACHE_GET_AND_PUT >>>> OP_CACHE_GET_AND_REPLACE >>>> OP_CACHE_GET_AND_PUT_IF_ABSENT >>>> OP_CACHE_REPLACE >>>> OP_CACHE_REPLACE_IF_EQUALS >>>> >>>> >>>> >>>> On Tue, May 19, 2020 at 4:11 PM scriptnull <[email protected]> >>>> wrote: >>>> >>>>> Awesome, that's exactly the information that I needed. So we will have >>>>> to set >>>>> the flag byte while doing OP_CACHE_PUT. >>>>> >>>>> Do you know by any chance if there is support for setting expire times >>>>> for >>>>> multiple key-values while doing a OP_CACHE_PUT_ALL (opcode: 1004) >>>>> operation? >>>>> I am guessing the answer is no. >>>>> >>>>> Regards, >>>>> Vishnu Bharathi P >>>>> >>>>> >>>>> >>>>> -- >>>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >>>>> >>>>
