September 2019 - infinispan-issues

[JBoss JIRA] (ISPN-9962) Feature-packs should optionally depend on jdk-unsupported and sun.jdk

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9962?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9962: ----------------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33) > Feature-packs should optionally depend on jdk-unsupported and sun.jdk > --------------------------------------------------------------------- > > Key: ISPN-9962 > URL: https://issues.jboss.org/browse/ISPN-9962 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > Currently our feature-packs depend on both "sun.jdk" and "jdk.unsupported" in an inconsistent manner. For the latest versions of Wildfly, we need to use the latter, whilst for older ones we need to use the former. Therefore, for all modules that require access to unsupported classes, we must provide an optional dependency on both of the above modules. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9932) Avoid creating MarshallableEntry instances if no CacheWriter enabled

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9932?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9932: ----------------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33) > Avoid creating MarshallableEntry instances if no CacheWriter enabled > -------------------------------------------------------------------- > > Key: ISPN-9932 > URL: https://issues.jboss.org/browse/ISPN-9932 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > The (Dist)CacheWriterIntercepter is enabled if any loader/store is configured. The problem, is that the interceptor assumes that a CacheWriter is always configured. However, it is possible that only a CacheLoader has been configured, in which case when a write command visits the interceptor, MarshallableEntry instances are created unnecessarily in order to call the various PersistenceManager write operations. > To avoid unnecessary allocations and the marshalling of key/value/metadata that is never stored, we should ensure that calls to PersistenceManager write methods are only called if a CacheWriter is actually configured. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9915) JDBC publish Flowable should explicitly rollback connection

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9915?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9915: ----------------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33) > JDBC publish Flowable should explicitly rollback connection > ----------------------------------------------------------- > > Key: ISPN-9915 > URL: https://issues.jboss.org/browse/ISPN-9915 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > The Flowable for the JDBC store publisher sets `autoCommit(false)` in order for pagination to work as expected, however we never explicitly call commit or rollback on the connection, therefore the exact behaviour is determined by the underlying connection pool. Instead we should explicitly call rollback() on the connection after the publisher has finished, because the operation is read only. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9877) Nashorn and sun.scription modules optional for embedded feature-packs

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9877?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9877: ----------------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33) > Nashorn and sun.scription modules optional for embedded feature-packs > --------------------------------------------------------------------- > > Key: ISPN-9877 > URL: https://issues.jboss.org/browse/ISPN-9877 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 10.0.0.Alpha2, 9.4.5.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha3, 9.4.6.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9876) Commons and embedded feature-packs should utilise 1.3 schema for backwards-compatibility

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9876?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9876: ----------------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33) > Commons and embedded feature-packs should utilise 1.3 schema for backwards-compatibility > -------------------------------------------------------------------------------------------- > > Key: ISPN-9876 > URL: https://issues.jboss.org/browse/ISPN-9876 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 10.0.0.Alpha2, 9.4.5.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha3, 9.4.6.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9843) RocksDBStore should not write entire MarshalledEntry as store value

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9843?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9843: ----------------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33) > RocksDBStore should not write entire MarshalledEntry as store value > ------------------------------------------------------------------- > > Key: ISPN-9843 > URL: https://issues.jboss.org/browse/ISPN-9843 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha3 > > > Currently the RocksDBStore implementation writes an entire MarshalledEntry as the db's value. This is inefficient as it means the key is stored twice. Instead, a KeyValuePair of an entries value and metadata should be stored. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9599) DefaultCacheManager.getGlobalComponentRegistry should require ADMIN permission

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9599?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9599: ----------------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33) > DefaultCacheManager.getGlobalComponentRegistry should require ADMIN permission > ------------------------------------------------------------------------------ > > Key: ISPN-9599 > URL: https://issues.jboss.org/browse/ISPN-9599 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.3.3.Final, 9.4.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final, 9.4.17.Final > > > {{DefaultCacheManager.getGlobalComponentRegistry()}} allows invoking any component without additional permission checks, so it needs ADMIN permission. > {{DefaultCacheManager.getCacheManagerConfiguration()}} also allows access to some internal components, so it also needs ADMIN permission. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9592) Lockdown query internals

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9592?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9592: ----------------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33) > Lockdown query internals > ------------------------ > > Key: ISPN-9592 > URL: https://issues.jboss.org/browse/ISPN-9592 > Project: Infinispan > Issue Type: Task > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > > Many things in query implementation are left public although they are very prone to creating insidious bugs if accessed externally. These are not proper extension points and should be made package local or provided strictly via SearchManagerImplementor. > * Move SearchManager.purge(Class) method to SearchManagerImplementor > * DefaultSearchWorkCreator should be moved to org.infinispan.query.backend and made package local > * TransactionalEventTransactionContext is not used, can be removed, and its non-tx counterpart (NoTransactionContext) no longer has to be public > * all public methods in QueryInterceptor must be reviewed and made package local ASAP -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2575) Key Transformer registration is required on all nodes of the cluster, in case of custom keys

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-2575: ----------------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33) > Key Transformer registration is required on all nodes of the cluster, in case of custom keys > -------------------------------------------------------------------------------------------- > > Key: ISPN-2575 > URL: https://issues.jboss.org/browse/ISPN-2575 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 5.2.0.Beta5 > Reporter: Anna Manukyan > Assignee: Nistor Adrian > Priority: Minor > Fix For: 10.0.0.CR3 > > Attachments: ClusteredCacheTest.java > > > The case is the following: > I have a clustered cache on which I want to perform a search. I'm doing the following: > I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception: > java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer > When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager. > The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer() -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9322) Remove all usages of @IndexedField protostream annotation

by Pedro Zapata Fernandez (Jira)

[ https://issues.jboss.org/browse/ISPN-9322?page=com.atlassian.jira.plugin.... ] Pedro Zapata Fernandez updated ISPN-9322: ----------------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34 (was: DataGrid Sprint #33) > Remove all usages of @IndexedField protostream annotation > --------------------------------------------------------- > > Key: ISPN-9322 > URL: https://issues.jboss.org/browse/ISPN-9322 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 10.0.0.CR3 > > > This annotation is deprecated and should be replaced with @Field but we still have several usages in our test suite. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 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 September 2019