[infinispan-issues] [JBoss JIRA] (ISPN-9181) Remove compat mode from Remote Iterator
Gustavo Fernandes (JIRA)
issues at jboss.org
Thu Jun 7 01:25:00 EDT 2018
[ https://issues.jboss.org/browse/ISPN-9181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gustavo Fernandes updated ISPN-9181:
------------------------------------
Description:
The remote iterator has internal checks for compat mode and unmarshalls keys and values before running them to the filters (in case they're present), except when compat mode is present.
There should be a generic mechanism where the filter itself specifies in which format it wants to process the data. Something similar to {{useRawData()}} in the remote listeners, where each listener control the type of data should receive, either as Pojos or binary format.
Furthermode, there is a Cache Manager wide marshaller that is used to "unmarshall" filter paramers and objects. This marshaller should be removed and instead the MediaType info sent by clients should be used to select the right transcoder to convert to/from the storage format
was:
The remote iterator checks for compat mode and if present, unmarshalls keys and values before running them to the filters (in case they're present).
There should be a generic mechanism where the filter itself specifies in which format it wants to process the data. Something similar to {{useRawData()}} in the remote listeners, where each listener control the type of data should receive, either as Pojos or binary format.
Furthermode, there is a Cache Manager wide marshaller that is used to "unmarshall" filter paramers and objects. This marshaller should be removed and instead the MediaType info sent by clients should be used to select the right transcoder to convert to/from the storage format
> Remove compat mode from Remote Iterator
> ---------------------------------------
>
> Key: ISPN-9181
> URL: https://issues.jboss.org/browse/ISPN-9181
> Project: Infinispan
> Issue Type: Sub-task
> Components: Server
> Reporter: Gustavo Fernandes
>
> The remote iterator has internal checks for compat mode and unmarshalls keys and values before running them to the filters (in case they're present), except when compat mode is present.
> There should be a generic mechanism where the filter itself specifies in which format it wants to process the data. Something similar to {{useRawData()}} in the remote listeners, where each listener control the type of data should receive, either as Pojos or binary format.
> Furthermode, there is a Cache Manager wide marshaller that is used to "unmarshall" filter paramers and objects. This marshaller should be removed and instead the MediaType info sent by clients should be used to select the right transcoder to convert to/from the storage format
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the infinispan-issues
mailing list