March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11446) Always set a default request MediaType for caches

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11446?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11446: ------------------------------------- Status: Open (was: New) > Always set a default request MediaType for caches > ------------------------------------------------- > > Key: ISPN-11446 > URL: https://issues.redhat.com/browse/ISPN-11446 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 11.0.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > *Background*: when a cache is created, it does not have a default request type inside its internal Key/Value DataConversion objects, so no transcoding will be attempted during its operations. > When decorated with _{{.withMediaType(MediaType key, MediaType value)}}_, a new cache instance is produced setting the request type internally, and all operations will be converted from the storage media type to this request media type (when reading), or from the request media type to storage media type (when writing). > *Drawback*: When a cache is used through any remote endpoint, it is always decorated since remote clients are able to communicate the request format, but when a cache is used directly in the same JVM the request type is _null_, so no transcoding is done, unless the cache is decorated with the required type. > *Change*: This issue will change the default request type for all caches to _{{application/x-java-object}}_, so transcoding can be done in embedded caches without the need to decorate, it's enough to set the storage type in the configuration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11446) Always set a default request MediaType for caches

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-11446: ---------------------------------------- Summary: Always set a default request MediaType for caches Key: ISPN-11446 URL: https://issues.redhat.com/browse/ISPN-11446 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 11.0.0.Alpha2 Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes *Background*: when a cache is created, it does not have a default request type inside its internal Key/Value DataConversion objects, so no transcoding will be attempted during its operations. When decorated with _{{.withMediaType(MediaType key, MediaType value)}}_, a new cache instance is produced setting the request type internally, and all operations will be converted from the storage media type to this request media type (when reading), or from the request media type to storage media type (when writing). *Drawback*: When a cache is used through any remote endpoint, it is always decorated since remote clients are able to communicate the request format, but when a cache is used directly in the same JVM the request type is _null_, so no transcoding is done, unless the cache is decorated with the required type. *Change*: This issue will change the default request type for all caches to _{{application/x-java-object}}_, so transcoding can be done in embedded caches as well, without the need to decorate: it's enough to set the storage type in the configuration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8726) Implement the meta memcached protocol

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-8726?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-8726: ---------------------------------- Description: We should implement Memcached's meta commands https://github.com/memcached/memcached/wiki/MetaCommands These enhance the text protocol with all the features of the binary protocol (which has been deprecated) The implementation should use Infinispan's protocol-parser-generator was: In order to symmetrically provide security features to all the endpoints, the memcached endpoint needs to support the binary protocol as that is the only one that allows TLS encryption and SASL authn. https://github.com/memcached/memcached/wiki/BinaryProtocolRevamped The implementation should use Infinispan's protocol-parser-generator > Implement the meta memcached protocol > ------------------------------------- > > Key: ISPN-8726 > URL: https://issues.redhat.com/browse/ISPN-8726 > Project: Infinispan > Issue Type: Enhancement > Components: Memcached, Server > Reporter: Tristan Tarrant > Assignee: Dmitry Volodin > Priority: Major > > We should implement Memcached's meta commands https://github.com/memcached/memcached/wiki/MetaCommands > These enhance the text protocol with all the features of the binary protocol (which has been deprecated) > The implementation should use Infinispan's protocol-parser-generator -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8726) Implement the meta memcached protocol

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-8726?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-8726: ---------------------------------- Summary: Implement the meta memcached protocol (was: Implement the binary memcached protocol) > Implement the meta memcached protocol > ------------------------------------- > > Key: ISPN-8726 > URL: https://issues.redhat.com/browse/ISPN-8726 > Project: Infinispan > Issue Type: Enhancement > Components: Memcached, Server > Reporter: Tristan Tarrant > Assignee: Dmitry Volodin > Priority: Major > > In order to symmetrically provide security features to all the endpoints, the memcached endpoint needs to support the binary protocol as that is the only one that allows TLS encryption and SASL authn. > https://github.com/memcached/memcached/wiki/BinaryProtocolRevamped > The implementation should use Infinispan's protocol-parser-generator -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11403) RestMetricsResource fails due to NettyTransportConnectionStats.getNumberOfGlobalConnections metrics not working with jmx disabled

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11403?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11403: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > RestMetricsResource fails due to NettyTransportConnectionStats.getNumberOfGlobalConnections metrics not working with jmx disabled > --------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-11403 > URL: https://issues.redhat.com/browse/ISPN-11403 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 11.0.0.Alpha1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > NettyTransportConnectionStats depending on jmx being enabled is very very very very wrong. > Today's fix will just allow mp metrics export to work, and these stats be 0 if jmx is not enabled. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11389) Deprecate EmbeddedCacheManager.getStats() method because CacheContainerStats is already deprecated

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11389?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11389: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Deprecate EmbeddedCacheManager.getStats() method because CacheContainerStats is already deprecated > -------------------------------------------------------------------------------------------------- > > Key: ISPN-11389 > URL: https://issues.redhat.com/browse/ISPN-11389 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.1.3.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11390) Non-components cannot export metrics

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11390?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11390: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Non-components cannot export metrics > ------------------------------------ > > Key: ISPN-11390 > URL: https://issues.redhat.com/browse/ISPN-11390 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, Server > Affects Versions: 10.1.3.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > AbstractProtocolServer's worker thread pool and the protocol are such examples. They expose managed attributes but those cannot be currently exported as microprofile metrics due to fact these are not registered in the component registry. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11388) Refactor CacheIgnoreManager - AbstractProtocolServer collaboration

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11388?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11388: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Refactor CacheIgnoreManager - AbstractProtocolServer collaboration > ------------------------------------------------------------------ > > Key: ISPN-11388 > URL: https://issues.redhat.com/browse/ISPN-11388 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 10.1.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > Given the interactions between CacheIgnoreManager and AbstractProtocolServer it seems that CacheIgnoreManager should be a global component in the registry of the EmbeddedCacheManager sitting behind the AbstractProtocolServer. It should be looked up from there, or better injected, rather than being received in ProtocolServer.start method. The start method also has an overloaded version that does not take a CacheIgnoreManager to support tests the do not need it. This lack of orthogonality is annoyoing. > Another aspect to refactor: the startInternal method receives parametters that it assigns to fields. It seems that this should have been done already in the start method. That would get rid of some clunky hacks and some comments/excuses for the said hacks. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11438) Additional metric registration config option: namesAsTags

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11438?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11438: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Additional metric registration config option: namesAsTags > --------------------------------------------------------- > > Key: ISPN-11438 > URL: https://issues.redhat.com/browse/ISPN-11438 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > Boolean options, false by default. If enabled it results in the cache manager name and cache name being added as tags rather than being included in the metric name. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11358) Detail cache (how to display config)

by Ming Zhong (Jira)

[ https://issues.redhat.com/browse/ISPN-11358?page=com.atlassian.jira.plugi... ] Ming Zhong updated ISPN-11358: ------------------------------ Description: Page position: Cluster>CacheDetails>Configuration Detail cache today does not display the configuration of the cache (JSON or XML format - at choice) I would like to know which is the best place to display that (detail of the cache, the list of caches with a modal?) Display the cache configuration (detail and/or list) * Be able to display the configuration of a cache * GET /rest/v2/caches/{name}?action=config was: Page position: Cluster>CacheDetails>cache configuration Detail cache today does not display the configuration of the cache (JSON or XML format - at choice) I would like to know which is the best place to display that (detail of the cache, the list of caches with a modal?) Display the cache configuration (detail and/or list) * Be able to display the configuration of a cache * GET /rest/v2/caches/{name}?action=config > Detail cache (how to display config) > ------------------------------------ > > Key: ISPN-11358 > URL: https://issues.redhat.com/browse/ISPN-11358 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Reporter: Katia Aresti > Assignee: Ming Zhong > Priority: Major > Labels: console-ng > > Page position: Cluster>CacheDetails>Configuration > Detail cache today does not display the configuration of the cache (JSON or XML format - at choice) > I would like to know which is the best place to display that (detail of the cache, the list of caches with a modal?) > Display the cache configuration (detail and/or list) > * Be able to display the configuration of a cache > * GET /rest/v2/caches/{name}?action=config -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2020