[JBoss JIRA] (ISPN-8449) Separate the marshalling of the remote QueryRequest/QueryReponse objects and the client marshaller
by Nistor Adrian (Jira)
[ https://issues.jboss.org/browse/ISPN-8449?page=com.atlassian.jira.plugin.... ]
Nistor Adrian updated ISPN-8449:
--------------------------------
Labels: SearchNG (was: )
> Separate the marshalling of the remote QueryRequest/QueryReponse objects and the client marshaller
> --------------------------------------------------------------------------------------------------
>
> Key: ISPN-8449
> URL: https://issues.jboss.org/browse/ISPN-8449
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Querying
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Labels: SearchNG
>
> Remote query currently uses the client marshaller for marshalling the query request/response objects. This is currently hardcoded to work for the protobuf and jboss-marshalling case, but if the client's marshaller is changed to something else this will break.
> The solution would be to separate the marshalling. The query request/response object should be marshalled using protobuf regardless of what client marshaller is configured. Only the payload of the reponse should be marshalled using the client marshaller.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (ISPN-10255) Documentation about Near cache eviction
by Gustavo Lira e Silva (Jira)
Gustavo Lira e Silva created ISPN-10255:
-------------------------------------------
Summary: Documentation about Near cache eviction
Key: ISPN-10255
URL: https://issues.jboss.org/browse/ISPN-10255
Project: Infinispan
Issue Type: Bug
Components: Documentation-Core
Affects Versions: 9.4.14.Final
Reporter: Gustavo Lira e Silva
The following section is not 100% right:
When the maximum is reached, near cached entries are evicted using a least-recently-used (LRU) algorithm
Since JDG 7.2 eviction algorithm use TinyLFU via Caffeine. Maybe this section could be removed because this information is totally irrelevant for the user.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months