[JBoss JIRA] (ISPN-11964) WARN about unknown cache encoding
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11964?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11964:
-------------------------------------
Status: Open (was: New)
> WARN about unknown cache encoding
> ----------------------------------
>
> Key: ISPN-11964
> URL: https://issues.redhat.com/browse/ISPN-11964
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Server
> Affects Versions: 11.0.0.CR1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> A special MediaType ''application/unknown" is used when the cache hasn't an <encoding> configuration and its encoding cannot be guessed.
> For 11.0.0.Final, this should result in a WARNING since conversions with unknown format depends on "user marshaller" and can be done only in a best effort basis
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-10733) Operator Docs: Spec updates
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-10733?page=com.atlassian.jira.plugi... ]
Donald Naro closed ISPN-10733.
------------------------------
Resolution: Out of Date
> Operator Docs: Spec updates
> ---------------------------
>
> Key: ISPN-10733
> URL: https://issues.redhat.com/browse/ISPN-10733
> Project: Infinispan
> Issue Type: Task
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> https://github.com/infinispan/infinispan-operator/issues/169
> Vittorio's comment in the issue. There are two main use cases:
> Change that reflects to a statefulset.spec.containers field. This automatically triggers a redeploy. i.e. spec.container fields. - This doesn't need documentation because it's assumed that if you change the statefulset, the Operator redeploys the pods.
> Change to other field or resource. In this case it would be good to have a list of 'redeployIfChanged' objects and check against it if a redeploy is needed or not. - Possibly need to document the list of objects.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11943) Single MediaType ignored in JSON config
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-11943?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated ISPN-11943:
---------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Single MediaType ignored in JSON config
> ---------------------------------------
>
> Key: ISPN-11943
> URL: https://issues.redhat.com/browse/ISPN-11943
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 11.0.0.CR1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> The recently introduced single MediaType config for both keys and values is being ignored when creating a cache from JSON:
> {code:json}
> {
> "distributed-cache":{
> "encoding":{
> "media-type":"application/x-protostream"
> }
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11974) Remove GenericJbossMarshaller automatic configuration
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11974?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-11974:
--------------------------------
Sprint: DataGrid Sprint #45
> Remove GenericJbossMarshaller automatic configuration
> -----------------------------------------------------
>
> Key: ISPN-11974
> URL: https://issues.redhat.com/browse/ISPN-11974
> Project: Infinispan
> Issue Type: Task
> Components: Configuration, Hot Rod
> Affects Versions: 11.0.0.CR1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Currently if the {{infinispan-jboss-marshalling}} module is on the client classpath we automatically configure the client marshaller to be {{GenericJBossMarshaller}}. This causes issues with our testsuite, as the module is often on the classpath. Furthermore, we want users to start transitioning away from JBoss Marshalling. Therefore, from Infinispan 12 we should no automatically configure this marshaller if the module is present.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11974) Remove GenericJbossMarshaller automatic configuration
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11974?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-11974:
--------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8445
> Remove GenericJbossMarshaller automatic configuration
> -----------------------------------------------------
>
> Key: ISPN-11974
> URL: https://issues.redhat.com/browse/ISPN-11974
> Project: Infinispan
> Issue Type: Task
> Components: Configuration, Hot Rod
> Affects Versions: 11.0.0.CR1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Currently if the {{infinispan-jboss-marshalling}} module is on the client classpath we automatically configure the client marshaller to be {{GenericJBossMarshaller}}. This causes issues with our testsuite, as the module is often on the classpath. Furthermore, we want users to start transitioning away from JBoss Marshalling. Therefore, from Infinispan 12 we should no automatically configure this marshaller if the module is present.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11974) Remove GenericJbossMarshaller automatic configuration
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11974?page=com.atlassian.jira.plugi... ]
Work on ISPN-11974 started by Ryan Emerson.
-------------------------------------------
> Remove GenericJbossMarshaller automatic configuration
> -----------------------------------------------------
>
> Key: ISPN-11974
> URL: https://issues.redhat.com/browse/ISPN-11974
> Project: Infinispan
> Issue Type: Task
> Components: Configuration, Hot Rod
> Affects Versions: 11.0.0.CR1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Currently if the {{infinispan-jboss-marshalling}} module is on the client classpath we automatically configure the client marshaller to be {{GenericJBossMarshaller}}. This causes issues with our testsuite, as the module is often on the classpath. Furthermore, we want users to start transitioning away from JBoss Marshalling. Therefore, from Infinispan 12 we should no automatically configure this marshaller if the module is present.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months