[Red Hat JIRA] (ISPN-11966) Deprecate application/x-java-object in the REST API
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11966?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11966:
-----------------------------------
Fix Version/s: 12.1.0.Final
(was: 12.0.0.Final)
> Deprecate application/x-java-object in the REST API
> ---------------------------------------------------
>
> Key: ISPN-11966
> URL: https://issues.redhat.com/browse/ISPN-11966
> Project: Infinispan
> Issue Type: Task
> Components: REST
> Affects Versions: 11.0.0.CR1
> Reporter: Dan Berindei
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 12.1.0.Final
>
>
> The REST server supports request header {{Key-Content-Type}}, which changes the meaning of the key in the request URI to be encoded in different media types.
> One of the supported media types is {{application/x-java-object}}, which parses Java primitives as if they were Java literals, with special handling for {{String}} and {{byte[]}}. The parsing rules are ad-hoc and undocumented, so I suggest we stop supporting them.
> Users who want a readable URI should instead use write the key as JSON and rely on the server to transcode between JSON and the cache storage media type.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (ISPN-11889) Remove deprecated parser attributes
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11889?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11889:
-----------------------------------
Fix Version/s: 12.1.0.Final
(was: 12.0.0.Final)
> Remove deprecated parser attributes
> -----------------------------------
>
> Key: ISPN-11889
> URL: https://issues.redhat.com/browse/ISPN-11889
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 11.0.0.Dev05
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.1.0.Final
>
>
> Remove configuration attributes ASYNC_MARSHALLING, FLUSH_LOCK_TIMEOUT, QUEUE_FLUSH_INTERVAL, QUEUE_SIZE, REPLICATION_QUEUE_EXECUTOR, SHUTDOWN_TIMEOUT and their handling in the parser, they have not been supported since 9.0.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (ISPN-12113) HTTP authentication with only Digest SHA mechanisms fails
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12113?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12113:
-----------------------------------
Fix Version/s: 12.1.0.Final
(was: 12.0.0.Final)
> HTTP authentication with only Digest SHA mechanisms fails
> ---------------------------------------------------------
>
> Key: ISPN-12113
> URL: https://issues.redhat.com/browse/ISPN-12113
> Project: Infinispan
> Issue Type: Bug
> Reporter: Francisco De Melo Junior
> Assignee: Francisco De Melo Junior
> Priority: Minor
> Labels: authentication, encryption, rest
> Fix For: 12.1.0.Final
>
>
> {code:xml}
> <cache-container name="clustered" default-cache="sessionCache" statistics="true">
> <transport stack="tcp-stack" site="z9" cluster="clustered" node-name="rhdgserver" />
> <security>
> <authorization>
> <identity-role-mapper />
> <role name="admin" permissions="ALL" />
> <role name="reader" permissions="READ" />
> <role name="writer" permissions="WRITE" />
> </authorization>
> </security>
> <metrics gauges="true" histograms="true" />
> </cache-container>
> (...)
> <endpoints socket-binding="default" security-realm="default">
> <hotrod-connector name="hotrod">
> <authentication>
> <sasl server-name="rhdgserver" mechanisms="DIGEST-SHA-256" qop="auth" />
> </authentication>
> </hotrod-connector>
> <rest-connector name="rest">
> <authentication mechanisms="DIGEST-SHA-256"/>
> </rest-connector>
> </endpoints>
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (ISPN-12037) JUnit-friendly replacement for MultipleCacheManagerTest
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12037?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12037:
-----------------------------------
Fix Version/s: 12.1.0.Final
(was: 12.0.0.Final)
> JUnit-friendly replacement for MultipleCacheManagerTest
> -------------------------------------------------------
>
> Key: ISPN-12037
> URL: https://issues.redhat.com/browse/ISPN-12037
> Project: Infinispan
> Issue Type: Task
> Components: Core, Test Suite
> Affects Versions: 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.1.0.Final
>
>
> Core tests that need one more more cache managers extend either {{SingleCacheManagerTest}} or {{MultipleCacheManagersTest}}. Many other modules' tests do the same for convenience.
> We would like to eventually move all modules to JUnit, and having an alternative to MCMT that can be used from either JUnit or TestNG and can support an incremental migration is the first step.
> The starting plan is for a {{TestCluster}} class for building and interacting with clusters including features from MCMT/TestingUtil/TestCacheManagerFactory/BasePartitionHandlingTest.
> Assertions like {{assertLocked()}}, {{assertIsInL1()}} etc. would be in separate classes, ideally with AssertJ-like {{assertThat}} static methods.
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (ISPN-12115) CacheContainerAdmin should allow defining configurations
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12115?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12115:
-----------------------------------
Fix Version/s: 12.1.0.Final
(was: 12.0.0.Final)
> CacheContainerAdmin should allow defining configurations
> --------------------------------------------------------
>
> Key: ISPN-12115
> URL: https://issues.redhat.com/browse/ISPN-12115
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Hot Rod, Server
> Affects Versions: 11.0.1.Final
> Reporter: Dan Berindei
> Priority: Major
> Fix For: 12.1.0.Final
>
>
> {{EmbeddedCacheManagerAdmin}} and {{RemoteCacheManagerAdmin}} allow creating a cache with a complete configuration or with an existing configuration template.
> It should be possible to define a configuration (template?) without a cache, so users/applications can define a common configuration and then reference it by name.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (ISPN-12048) Improve Cross-Site statistics
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12048?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12048:
-----------------------------------
Fix Version/s: 12.1.0.Final
(was: 12.0.0.Final)
> Improve Cross-Site statistics
> -----------------------------
>
> Key: ISPN-12048
> URL: https://issues.redhat.com/browse/ISPN-12048
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 11.0.0.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 12.1.0.Final
>
>
> Improve the cross-site statistics by adding a per-cache/site pair. Example:
> * sender site
> ** Cache_A
> *** Site_b (min/avg/max rtt, nr_requests_sent)
> ** Cache_B
> *** Site_b (min/avg/max rtt, nr_requests_sent)
> *** Site_c (min/avg/max rtt, nr_requests_sent)
> * Receiver site
> ** Cache_C
> *** Site_a (nr_requests_received)
> *** Site_c (nr_requests_received)
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months