[JBoss JIRA] (ISPN-11912) Per-cache Hot Rod client configuration support for caches with . in name
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-11912:
--------------------------------------
Summary: Per-cache Hot Rod client configuration support for caches with . in name
Key: ISPN-11912
URL: https://issues.redhat.com/browse/ISPN-11912
Project: Infinispan
Issue Type: Enhancement
Components: Hot Rod
Affects Versions: 10.1.8.Final, 11.0.0.CR1
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Currently the infinispan.client.hotrod.cache.xxx.* properties, where xxx is the name of a cache, don't allow the use of `.` characters in the name.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (ISPN-11878) Embedded configuration builders should automatically be enabled when attributes configured
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11878?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-11878:
--------------------------------
Status: Open (was: Pull Request Sent)
> Embedded configuration builders should automatically be enabled when attributes configured
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-11878
> URL: https://issues.redhat.com/browse/ISPN-11878
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration
> Affects Versions: 11.0.0.Dev05
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Currently it's neccessary for a user to do the following to configure the global state, as well serveral other configuration elements:
> {{globalBuilder.globalState().enable().persistentLocation(location)}}
> However the configuration of {{persistentLocation}} should be sufficient to enable the global state, i.e. the following should result in enabled(true) being called:
> {{globalBuilder.globalState().persistentLocation(location);}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (ISPN-11878) Embedded configuration builders should automatically be enabled when attributes configured
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11878?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-11878:
--------------------------------
Fix Version/s: 12.0.0.Final
(was: 11.0.0.Final)
> Embedded configuration builders should automatically be enabled when attributes configured
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-11878
> URL: https://issues.redhat.com/browse/ISPN-11878
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration
> Affects Versions: 11.0.0.Dev05
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Currently it's neccessary for a user to do the following to configure the global state, as well serveral other configuration elements:
> {{globalBuilder.globalState().enable().persistentLocation(location)}}
> However the configuration of {{persistentLocation}} should be sufficient to enable the global state, i.e. the following should result in enabled(true) being called:
> {{globalBuilder.globalState().persistentLocation(location);}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (ISPN-11911) Support iterator for RemoteQueries
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-11911:
----------------------------------------
Summary: Support iterator for RemoteQueries
Key: ISPN-11911
URL: https://issues.redhat.com/browse/ISPN-11911
Project: Infinispan
Issue Type: Feature Request
Reporter: Gustavo Fernandes
Query introduced an iterator in ISPN 11 when CacheQuery was deprecated, but it currently does not work for RemoteQueries
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (ISPN-11910) Server should see application/octet-stream as protostream
by Dan Berindei (Jira)
Dan Berindei created ISPN-11910:
-----------------------------------
Summary: Server should see application/octet-stream as protostream
Key: ISPN-11910
URL: https://issues.redhat.com/browse/ISPN-11910
Project: Infinispan
Issue Type: Enhancement
Components: Server
Affects Versions: 11.0.0.CR1
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 11.0.0.Final
The server, and Infinispan in general, should use the user marshaller to read {{application/octet-stream}} and {{application/unknown}} data.
ISPN-10433 added a hack in the server (for backwards compatibility, I assume): if {{jboss-marshalling}} is on the classpath, {{org.infinispan.server.core.LifecycleCallbacks.cacheManagerStarting()}} changes the marshaller for {{application/unknown}} (but not for {{application/octet-stream}}) to {{GenericJBossMarshaller}}.
This means that {{server/core}}, {{server/hotrod}}, and {{client/hotrod-client}} tests see {{application/unknown}} as protostream, but the server distribution in {{server/runtime}} always includes {{jboss-marshalling}}, so the server distribution sees {{application/unknown}} as {{GenericJBossMarshaller}} data.
It would be much better if the server always used the user marshaller for {{application/unknown}}, and when a user needs backwards compatibility between a new server and an old client, they should configure {{GenericJBossMarshaller}} in the server.
In addition, new clients should not use {{application/unknown}} unless the marshaller does not implement {{getMediaType()}}: they know the marshaller's media type, and they should send it to the server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months