Has there been a request for event listeners for the thin clients? I am
happy to roll my own implementation of the nearcache if I can get the
events of when cache items within the cluster are added, modified, or
deleted.
On Thu, May 21, 2020 at 2:29 PM Marty Jones wrote:
> Honestly near ca
the explanation.
>>> Yes, this is a good feature, and I've had this in mind for some time.
>>>
>>> Ticket filed: https://issues.apache.org/jira/browse/IGNITE-13037
>>> There are no immediate plans, but I think there is a possibility to
>>> achieve this by the end of
I understand the expiration policies but my question is about automatically
expiring a cache entry when an external event occurs such as a database
table column changes.
On Wed, May 20, 2020 at 9:49 AM akorensh wrote:
> Hi,
> Take a look at: https://apacheignite.readme.io/docs/expiry-policies
How do you guys handle invalidating cache items when the underlying data is
changed within say a database you are using to create cache items with?
ase 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 wrote:
>
>> I am not seeing that option in the ASP.NET thin client. Thi
I am not seeing that option in the ASP.NET thin client. This is how I
accomplished setting an expiration policy:
ICacheClient cache = igniteClient.GetCache("testCache");
cache.WithExpiryPolicy(new ExpiryPolicy(TimeSpan.FromSeconds(15), null,
null))
.Put("test1", new CacheItemEntry() {
The use case is having a local cache that stores most widely used cache
items in memory on server instead of having the network expense of pulling
them down every time they are requested. The main thing is the near cache
has to support removing cache items that have expired on the server.
The
