January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11231) Transcoder lookup is inefficient

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11231?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11231: -------------------------------- Fix Version/s: 9.4.18.Final > Transcoder lookup is inefficient > -------------------------------- > > Key: ISPN-11231 > URL: https://issues.redhat.com/browse/ISPN-11231 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.17.Final, 10.1.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.18.Final, 11.0.0.Alpha1 > > > {{EncoderRegistryImpl}} stores transcoders in a set, without any lookup optimization because it assumes the number of transcoders is small. > However, {{InternalCacheFactory.bootstrap()}} registers a "different" {{TranscoderMarshallerAdapter}} for each cache, even though they all delegate to the same global marshaller. > I believe the global marshaller transcoder adapter should be registered only once in {{EncoderRegistryFactory}}, and ideally we should have a way of looking up transcoders by media types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11246) Invoking a write operation with a loader should not retrieve value

by Will Burns (Jira)

Will Burns created ISPN-11246: --------------------------------- Summary: Invoking a write operation with a loader should not retrieve value Key: ISPN-11246 URL: https://issues.redhat.com/browse/ISPN-11246 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Reporter: Will Burns We have the notion of a Loader and a Store. If the user has configured a Loader and not a store, we should not retrieve the previous value when doing a write operation. This is normally used with a remove method to remove some in memory contents (as you can't write to a Loader). But in this case there is no reason to return the previous value from the Loader. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11231) Transcoder lookup is inefficient

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11231?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11231: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7801, https://github.com/infinispan/infinispan/pull/7802 > Transcoder lookup is inefficient > -------------------------------- > > Key: ISPN-11231 > URL: https://issues.redhat.com/browse/ISPN-11231 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.17.Final, 10.1.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Alpha1 > > > {{EncoderRegistryImpl}} stores transcoders in a set, without any lookup optimization because it assumes the number of transcoders is small. > However, {{InternalCacheFactory.bootstrap()}} registers a "different" {{TranscoderMarshallerAdapter}} for each cache, even though they all delegate to the same global marshaller. > I believe the global marshaller transcoder adapter should be registered only once in {{EncoderRegistryFactory}}, and ideally we should have a way of looking up transcoders by media types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11141) Spring Boot 2.2.2

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11141?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11141: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Spring Boot 2.2.2 > ----------------- > > Key: ISPN-11141 > URL: https://issues.redhat.com/browse/ISPN-11141 > Project: Infinispan > Issue Type: Component Upgrade > Components: Spring Integration > Affects Versions: 9.4.16.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9784) Remove Distributed Executor

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-9784?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-9784: ------------------------------ Fix Version/s: 9.4.18.Final > Remove Distributed Executor > --------------------------- > > Key: ISPN-9784 > URL: https://issues.redhat.com/browse/ISPN-9784 > Project: Infinispan > Issue Type: Sub-task > Components: Clustered Executor > Affects Versions: 10.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta1, 10.0.0.Final, 9.4.18.Final > > > Remove Distributed Executor in favor of Clustered Executor -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11245) default logging is with simplified classnames "c{1}" but full names are expected

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-11245?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink updated ISPN-11245: ------------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7800 pattern is now the full category > default logging is with simplified classnames "c{1}" but full names are expected > -------------------------------------------------------------------------------- > > Key: ISPN-11245 > URL: https://issues.redhat.com/browse/ISPN-11245 > Project: Infinispan > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Major > > It will be confusing if the class names are not fully shown because > - not clear which part is logging (jgroups, infinispan, custom classes) > - infinispan classes might be not unique > - application classes might use similar names to infinispan > - application classes might not have unique names > For this the full category should be shown as before -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11245) default logging is with simplified classnames "c{1}" but full names are expected

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-11245?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink reassigned ISPN-11245: --------------------------------------- Assignee: Wolf-Dieter Fink > default logging is with simplified classnames "c{1}" but full names are expected > -------------------------------------------------------------------------------- > > Key: ISPN-11245 > URL: https://issues.redhat.com/browse/ISPN-11245 > Project: Infinispan > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Major > > It will be confusing if the class names are not fully shown because > - not clear which part is logging (jgroups, infinispan, custom classes) > - infinispan classes might be not unique > - application classes might use similar names to infinispan > - application classes might not have unique names > For this the full category should be shown as before -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11245) default logging is with simplified classnames "c{1}" but full names are expected

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-11245?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink updated ISPN-11245: ------------------------------------ Status: Open (was: New) > default logging is with simplified classnames "c{1}" but full names are expected > -------------------------------------------------------------------------------- > > Key: ISPN-11245 > URL: https://issues.redhat.com/browse/ISPN-11245 > Project: Infinispan > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Major > > It will be confusing if the class names are not fully shown because > - not clear which part is logging (jgroups, infinispan, custom classes) > - infinispan classes might be not unique > - application classes might use similar names to infinispan > - application classes might not have unique names > For this the full category should be shown as before -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11245) default logging is with simplified classnames "c{1}" but full names are expected

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-11245?page=com.atlassian.jira.plugi... ] Work on ISPN-11245 started by Wolf-Dieter Fink. ----------------------------------------------- > default logging is with simplified classnames "c{1}" but full names are expected > -------------------------------------------------------------------------------- > > Key: ISPN-11245 > URL: https://issues.redhat.com/browse/ISPN-11245 > Project: Infinispan > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Major > > It will be confusing if the class names are not fully shown because > - not clear which part is logging (jgroups, infinispan, custom classes) > - infinispan classes might be not unique > - application classes might use similar names to infinispan > - application classes might not have unique names > For this the full category should be shown as before -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11245) default logging is with simplified classnames "c{1}" but full names are expected

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-11245: --------------------------------------- Summary: default logging is with simplified classnames "c{1}" but full names are expected Key: ISPN-11245 URL: https://issues.redhat.com/browse/ISPN-11245 Project: Infinispan Issue Type: Enhancement Reporter: Wolf-Dieter Fink It will be confusing if the class names are not fully shown because - not clear which part is logging (jgroups, infinispan, custom classes) - infinispan classes might be not unique - application classes might use similar names to infinispan - application classes might not have unique names For this the full category should be shown as before -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020