May 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9179) Remove compat mode from the REST Server

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9179?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9179: ------------------------------------ Status: Open (was: New) > Remove compat mode from the REST Server > --------------------------------------- > > Key: ISPN-9179 > URL: https://issues.jboss.org/browse/ISPN-9179 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9179) Remove compat mode from the REST Server

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9179?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9179: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5995 > Remove compat mode from the REST Server > --------------------------------------- > > Key: ISPN-9179 > URL: https://issues.jboss.org/browse/ISPN-9179 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9184) Remove compat mode from Remote Listener

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9184?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9184: ------------------------------------ Component/s: Listeners > Remove compat mode from Remote Listener > --------------------------------------- > > Key: ISPN-9184 > URL: https://issues.jboss.org/browse/ISPN-9184 > Project: Infinispan > Issue Type: Sub-task > Components: Listeners > Reporter: Gustavo Fernandes > > Remote Listeners uses compat mode checks in plenty of places to convert between storage and pojo format, and apart from that have a cache manager wide "event marshaller" used to unmarshal params for filters used in events, falling back to GenericJbossMarshaller when the marshaller is not set. > It should not use a global marshaller and should not hardcode JbossMarshaller, instead the remote listener themselves should have a mechanism of choosing the format of the data, similar to "useRawData" (where one can choose to receive events in a marshalled or unmarshaled way). One way of doing it is to supply a MediaType in the listener with the desired format. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9184) Remove compat mode from Remote Listener

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-9184: --------------------------------------- Summary: Remove compat mode from Remote Listener Key: ISPN-9184 URL: https://issues.jboss.org/browse/ISPN-9184 Project: Infinispan Issue Type: Sub-task Reporter: Gustavo Fernandes Remote Listeners uses compat mode checks in plenty of places to convert between storage and pojo format, and apart from that have a cache manager wide "event marshaller" used to unmarshal params for filters used in events, falling back to GenericJbossMarshaller when the marshaller is not set. It should not use a global marshaller and should not hardcode JbossMarshaller, instead the remote listener themselves should have a mechanism of choosing the format of the data, similar to "useRawData" (where one can choose to receive events in a marshalled or unmarshaled way). One way of doing it is to supply a MediaType in the listener with the desired format. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9180) Remove compat mode from Remote Query

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9180?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9180: ------------------------------------ Component/s: Remote Querying > Remove compat mode from Remote Query > ------------------------------------ > > Key: ISPN-9180 > URL: https://issues.jboss.org/browse/ISPN-9180 > Project: Infinispan > Issue Type: Sub-task > Components: Remote Querying > Reporter: Gustavo Fernandes > > The ProtobufMetadataManager is configured internally using compat mode plus the CompatibilityProtostreamMarshaller as a marshaller. This requires that HR clients use the protostream marshaller to register .proto files, since otheriwse the server cannot unmarshall it. > The ProtobufMetadataManager cache should rely instead on the MediaType sent by the HR client and convert the incoming content to java object (String) on the fly, as long as the server supports conversion between the content produced by marshaller and java object. > Apart from that, there are multiple places in the code that registers/instantiates/configures objects based on the compat mode marshaller, and assume all content will be unmarshalled by this marshaller. It should instead rely on the MediaType information sent by the HR client and do the conversion on the fly, this would allow indexing and querying in multiple formats as long as the storage format is supported and the conversion between the input/storage is supported by the server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9181) Remove compat mode from Remote Iterator

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9181?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9181: ------------------------------------ Component/s: Server > 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 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 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9182) Remove compat mode from Tasks and Scripts

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9182?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9182: ------------------------------------ Component/s: Tasks > Remove compat mode from Tasks and Scripts > ----------------------------------------- > > Key: ISPN-9182 > URL: https://issues.jboss.org/browse/ISPN-9182 > Project: Infinispan > Issue Type: Sub-task > Components: Tasks > Reporter: Gustavo Fernandes > > Both script and tasks hardcode GenericJbossMarshaller in several places, and use it to unmarshall parameters and user data when executing code. If the client uses a different marshaller, it breaks. > Both should rely instead of the MediaType sent by the Hot Rod client in order to convert from and to the storage format. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9183) Replace <eviction> with <memory> in 2LC configs

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9183?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-9183: ------------------------------ Status: Open (was: New) > Replace <eviction> with <memory> in 2LC configs > ----------------------------------------------- > > Key: ISPN-9183 > URL: https://issues.jboss.org/browse/ISPN-9183 > Project: Infinispan > Issue Type: Task > Components: Hibernate Cache > Affects Versions: 9.3.0.Beta1 > Reporter: Radim Vansa > Assignee: Radim Vansa > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9183) Replace <eviction> with <memory> in 2LC configs

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9183?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-9183: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5994 > Replace <eviction> with <memory> in 2LC configs > ----------------------------------------------- > > Key: ISPN-9183 > URL: https://issues.jboss.org/browse/ISPN-9183 > Project: Infinispan > Issue Type: Task > Components: Hibernate Cache > Affects Versions: 9.3.0.Beta1 > Reporter: Radim Vansa > Assignee: Radim Vansa > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9181) Remove compat mode from Remote Iterator

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9181?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9181: ------------------------------------ Description: 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 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. > Remove compat mode from Remote Iterator > --------------------------------------- > > Key: ISPN-9181 > URL: https://issues.jboss.org/browse/ISPN-9181 > Project: Infinispan > Issue Type: Sub-task > Reporter: Gustavo Fernandes > > 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 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2018