June 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9976) Query still has a hard dependency on Elasticsearch

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9976?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9976: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > Query still has a hard dependency on Elasticsearch > -------------------------------------------------- > > Key: ISPN-9976 > URL: https://issues.jboss.org/browse/ISPN-9976 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > 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 > > > ISPN-9795 Made the {{org.hibernate.search.elasticsearch}} module optional in our feature-packs, however in `infinispan-query`there is an unchecked call to {{org.hibernate.search.elasticsearch.bridge.builtin.impl.ElasticsearchDateBridge}} regardless of whether Elasticsearch is actually available on the classpath. This results in a {{NoClassDefFoundError}} whenever {{HibernateSearchPropertyHelper#convertToPropertyType}} is called and Elasticsearch is not available. For example when deploying the wfly-modules to a wfly instance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9960) JavaDocs cleanups

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9960?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9960: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > JavaDocs cleanups > ----------------- > > Key: ISPN-9960 > URL: https://issues.jboss.org/browse/ISPN-9960 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > The JavaDocs contain several broken entities (espcially > < and variations) as well as a number of broken links/sees (caused by prior refactorings). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9498) Index filesystem paths in server should point to data directory

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9498?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9498: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1) > Index filesystem paths in server should point to data directory > --------------------------------------------------------------- > > Key: ISPN-9498 > URL: https://issues.jboss.org/browse/ISPN-9498 > Project: Infinispan > Issue Type: Bug > Components: Indexing, OpenShift, Server > Affects Versions: 9.4.0.CR1, 9.3.3.Final > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > Priority: Major > > Certain indexing configurations result in using filesystem as index storage. > When running such configurations in a server environment, filesystem path should be somewhere within the server's data directory. This is the natural place for such data. > When running in OpenShift, server's data folder can be backed by a persistent volume. This means that the fileystem volume survives after restarts. > Plugging server's data directory is already happening for [file-store|https://github.com/infinispan/infinispan/blob/master/server/in...] and [rocksdb-store|https://github.com/infinispan/infinispan/blob/master/server...]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2575: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Beta1) > 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.Beta4 > > 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.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9397) Check TX support for remote caches

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9397?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9397: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1) > Check TX support for remote caches > ---------------------------------- > > Key: ISPN-9397 > URL: https://issues.jboss.org/browse/ISPN-9397 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Remote Protocols, Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Beta4, 10.0.0.Final > > > The {{RemoteCacheManager.getCache()}} methods would fail to return a transactional cache if the cache in server isn't transactional. It would throw an exception! {{NotTransactionalException}}? > The user can fallback to the non transaction case, example > {code:java} > try { > cache = remoteCacheManager.getCache("some-cache", TransactionMode.NON_XA); > } catch(NotTransactionalException e) { > cache = remoteCacheManager.getCache("some-cache", TransactionMode.NONE); > } > {code} > In addition, some helper method can be added to the {{RemoteCacheManager}} to avoid dealing with exceptions: > {code:java} > boolean supportsTransactions(String cacheName); > {code} > simple example: > {code:java} > boolean txCache = remoteCacheManager.supportsTransactions("some-cache"); > remoteCacheManager.getCache("some-cache", txCache ? TransactionMode.NON_XA : TransactionMode.NONE); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9592?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9592: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1) > 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.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9620) Rolling Upgrade Marshaller Changes

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9620: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1) > Rolling Upgrade Marshaller Changes > ---------------------------------- > > Key: ISPN-9620 > URL: https://issues.jboss.org/browse/ISPN-9620 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Loaders and Stores > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > In order to allow for compatibility between infinispan versions it is necessary for us to utilise a marshalling implementation at both the cluster (internal node-to-node communication) and persistence layer that is strictly defined but allows for future changes. This is necessary in order to facilitate both rolling and start/stop upgrades. Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9843?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9843: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > 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.12.1#712002)

6 years, 9 months

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9876?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9876: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > 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.12.1#712002)

6 years, 9 months

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9877?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9877: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > 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.12.1#712002)

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