[
https://issues.jboss.org/browse/ISPN-9393?page=com.atlassian.jira.plugin....
]
Diego Lovison edited comment on ISPN-9393 at 10/8/18 9:14 AM:
--------------------------------------------------------------
I am reopening the issue because the put operation always remove the entry from the near
cache
*InvalidatedNearRemoteCache*
{code:java}
public CompletableFuture<V> putAsync(K key, V value, long lifespan, TimeUnit
lifespanUnit, long maxIdleTime, TimeUnit maxIdleTimeUnit) {
if (maxIdleTime > 0L) {
log.nearCacheMaxIdleUnsupported();
}
CompletableFuture<V> ret = super.putAsync(key, value, lifespan, lifespanUnit,
maxIdleTime, maxIdleTimeUnit);
return ret.thenApply((v) -> {
this.nearcache.remove(key);
return v;
});
}
{code}
was (Author: dlovison):
I am reopening the issue because the put operation always remote the entry from the near
cache
*InvalidatedNearRemoteCache*
{code:java}
public CompletableFuture<V> putAsync(K key, V value, long lifespan, TimeUnit
lifespanUnit, long maxIdleTime, TimeUnit maxIdleTimeUnit) {
if (maxIdleTime > 0L) {
log.nearCacheMaxIdleUnsupported();
}
CompletableFuture<V> ret = super.putAsync(key, value, lifespan, lifespanUnit,
maxIdleTime, maxIdleTimeUnit);
return ret.thenApply((v) -> {
this.nearcache.remove(key);
return v;
});
}
{code}
getAsync() and getWithMetadata() does not check NearCache
---------------------------------------------------------
Key: ISPN-9393
URL:
https://issues.jboss.org/browse/ISPN-9393
Project: Infinispan
Issue Type: Bug
Components: Hot Rod, Remote Protocols
Reporter: Pedro Ruivo
Assignee: Tristan Tarrant
Priority: Blocker
Fix For: 9.4.0.Beta1, 9.4.0.CR3
In ISPN-8618, the java client was made async.
However, the {{getAsync()}} method isn't checking the {{NearCache}} anymore.
EDIT: {{getWithMetadata()}} isn't check the {{NearCache}}. I'm not sure if it is
supposed to check it or not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)