November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9513) Transformers registered via SearchManagerImplementor.registerKeyTransformer should be propagated in the cluster

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9513?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9513: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Transformers registered via SearchManagerImplementor.registerKeyTransformer should be propagated in the cluster > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9513 > URL: https://issues.jboss.org/browse/ISPN-9513 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 5.2.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.3.Final > > > This can be achieved in a similar manner QueryKnownClasses is used to propagate indexed entities to other nodes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9541) Module initialization is not thread-safe

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9541?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9541: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Module initialization is not thread-safe > ---------------------------------------- > > Key: ISPN-9541 > URL: https://issues.jboss.org/browse/ISPN-9541 > Project: Infinispan > Issue Type: Bug > Components: Core, Server > Affects Versions: 9.4.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.3.Final > > > In my ISPN-9127 fix I created a {{BasicComponentRegistry}} interface that represents a mostly-read-only collection of components. It has {{replaceComponent()}} method and a {{rewire()}} method for testing purposes, but it turns out modules were also relying on the ability to replace existing components in order to work. > Replacing global components is normally safe during the {{ModuleLifecycle.cacheManagerStarting()}}, because none of the components are started yet, so when a component starts later we can still start its dependencies first. But because some modules starts some global components, e.g. by calling {{manager.getCache(name)}}, that assumption breaks. > The {{infinispan-server-event-logger}} module is a bit more sneaky: it doesn't replace a component, instead it replaces the actual implementation of the event logger in the {{EventLogManager}} component. Events that happen before the module's {{cacheManagerStarting()}} or after {{cacheManagerStopping()}} will be silently dropped from the persistent event log. > I am investigating making the module a factory of factories. Instead of having a monolitic {{cacheManagerStarting()}} method, it could define a set of components that it can create, and a set of components that should be started before the cache manager is "running". We probably need a way to depend on other modules as well, maybe reusing the {{@Inject}} and {{@ComponentName}} annotations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9555) ComponentRegistry should enforce that registered components implement the interface/contract

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9555?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9555: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > ComponentRegistry should enforce that registered components implement the interface/contract > -------------------------------------------------------------------------------------------- > > Key: ISPN-9555 > URL: https://issues.jboss.org/browse/ISPN-9555 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Adrian Nistor > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.3.Final > > > ComponentRegistry.registerComponent(impl, interface) does not currently check that the impl really is assignable to the interface. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9657) Multimap jar is not OSGi compliant

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9657?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9657: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Multimap jar is not OSGi compliant > ---------------------------------- > > Key: ISPN-9657 > URL: https://issues.jboss.org/browse/ISPN-9657 > Project: Infinispan > Issue Type: Bug > Components: Multimap > Affects Versions: 9.4.0.Final > Reporter: Alain Picard > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Alpha2, 9.4.3.Final > > > Due to issues related to using the embedded jar (see [here|https://developer.jboss.org/message/986042#986042], when switching to individual jars, the multimap jar (infinispan-multimap-9.4.0.Final.jar) doesn't provide a valid OSGi manifest. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9646) Docs: Merge Details on Protocol Interoperability

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9646?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9646: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Docs: Merge Details on Protocol Interoperability > ------------------------------------------------ > > Key: ISPN-9646 > URL: https://issues.jboss.org/browse/ISPN-9646 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core, Marshalling, Remote Protocols > Affects Versions: 9.4.0.Final > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > Fix For: 10.0.0.Alpha2, 9.4.3.Final > > > The purpose of this task is to merge doc changes for protocol interoperability and compatibility mode into upstream docs from JDG. These changes should go into RHDG 7.3. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9610) Expose PersistenceManager availability via JMX

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9610?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9610: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Expose PersistenceManager availability via JMX > ---------------------------------------------- > > Key: ISPN-9610 > URL: https://issues.jboss.org/browse/ISPN-9610 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9587) Key Transformer registration via config

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9587?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9587: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Key Transformer registration via config > --------------------------------------- > > Key: ISPN-9587 > URL: https://issues.jboss.org/browse/ISPN-9587 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.3.Final > > > Under indexing config element: > {code} > <key-transformers> > <key-transformer key="org.infinispan.query.test.CustomKey" transformer="org.infinispan.query.test.CustomTransformer"/> > </key-transformers> > {code} > and also via the config builder API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9727) Ickle query ignores an IN clause if there is only one value

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9727?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9727: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Ickle query ignores an IN clause if there is only one value > ----------------------------------------------------------- > > Key: ISPN-9727 > URL: https://issues.jboss.org/browse/ISPN-9727 > Project: Infinispan > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Adrian Nistor > Priority: Critical > Fix For: 9.3.4.Final, 10.0.0.Alpha2, 9.4.3.Final > > > If an Ickl query has an IN clause in combination with another condition the IN clause seems completely ignored if it has only one value. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9719) Upgrade WildFly Core to 6.0.2

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9719?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9719: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Upgrade WildFly Core to 6.0.2 > ----------------------------- > > Key: ISPN-9719 > URL: https://issues.jboss.org/browse/ISPN-9719 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build, Server > Affects Versions: 9.4.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Alpha2, 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9726) Document max clause property on boolean query

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9726?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9726: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Document max clause property on boolean query > --------------------------------------------- > > Key: ISPN-9726 > URL: https://issues.jboss.org/browse/ISPN-9726 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Affects Versions: 10.0.0.Alpha1 > Reporter: Katia Aresti > Assignee: Adrian Nistor > Priority: Major > Fix For: 10.0.0.Alpha2, 9.4.3.Final > > > Document the ability to override org.apache.lucene.search.BooleanQuery.maxClauseCount using infinispan.query.lucene.max-boolean-clauses JVM system property. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 November 2018