November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10544) Remove dependencies on java.beans module

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10544?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10544: ----------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Remove dependencies on java.beans module > ----------------------------------------- > > Key: ISPN-10544 > URL: https://issues.jboss.org/browse/ISPN-10544 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR2 > > > Some Infinispan morning fitness to shed off java beans module -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10723) JMX registration cleanup

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10723?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10723: ----------------------------------- Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > JMX registration cleanup > ------------------------ > > Key: ISPN-10723 > URL: https://issues.jboss.org/browse/ISPN-10723 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.Final > > > - all jmx registration should happen via CacheManagerJmxRegistration/CacheJmxRegistration - we should not have other classes using JmxUtil.buildJmxDomain > - there are very few legitimate direct usages of JmxUtil.lookupMBeanServer; all else must go > - some registrations are not currently ResourceDMBeans; these need to be converted > - use of registerExternalMBean should be converted to registerMBean > - avoid performing the unregistration manually. Components registered with registerMBean will be unregistered automatically -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9083) Remove support for 'indexed_by_default' option in protobuf schemas

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9083?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9083: ---------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Remove support for 'indexed_by_default' option in protobuf schemas > ------------------------------------------------------------------ > > Key: ISPN-9083 > URL: https://issues.jboss.org/browse/ISPN-9083 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 10.0.0.Final > > > All the behaviour around this option must be removed and the option must be documented as no longer supported in Infinispan 10. > Usage of this option must trigger a warning. Should be entirely removed in 10.1 or some later version right after 10 - usages will be ignored after this point. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9186) Upgrade Protostream to 4.3.0.Alpha8

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9186?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9186: ---------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Upgrade Protostream to 4.3.0.Alpha8 > ----------------------------------- > > Key: ISPN-9186 > URL: https://issues.jboss.org/browse/ISPN-9186 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.Beta5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9322?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9322: ---------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > 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 > Fix For: 10.0.0.Final > > > 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.8#713008)

6 years, 1 month

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, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > 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.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10571) CORS usability issues

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10571?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10571: ----------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > CORS usability issues > --------------------- > > Key: ISPN-10571 > URL: https://issues.jboss.org/browse/ISPN-10571 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Labels: console-ng > Fix For: 10.0.0.CR2 > > > * OPTIONS is currently only handled by CORS for the pre-flight. Regular OPTIONS requests throw an error. > * By default, localhost is not allowed > * Specifying origin with '*' (all origins allowed) is not working -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (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, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > 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: Tristan Tarrant > 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.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10435) Support for serving static content

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10435?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10435: ----------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Support for serving static content > ---------------------------------- > > Key: ISPN-10435 > URL: https://issues.jboss.org/browse/ISPN-10435 > Project: Infinispan > Issue Type: Feature Request > Components: REST > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Labels: console-ng > Fix For: 10.0.0.CR2 > > > The REST endpoint should be able to serve the console from a static folder, respecting usual http headers sent by browsers to facilitate caching such as if-modified-since -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7889) BaseDistributionInterceptor.remoteGet may cause concurrency issues

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7889?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7889: ---------------------------------- 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, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (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, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > BaseDistributionInterceptor.remoteGet may cause concurrency issues > ------------------------------------------------------------------ > > Key: ISPN-7889 > URL: https://issues.jboss.org/browse/ISPN-7889 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Alpha1 > Reporter: Radim Vansa > Assignee: dan.berindei > Priority: Major > Fix For: 10.0.0.Alpha3, 9.4.6.Final > > > {{BaseDistributionInterceptor.remoteGet}} or any call that accesses the context in an async future handler that is called multiple times in parallel may lead to concurrent modifications of the context. > These calls are usually handled using {{CompletableFuture.allOf()}} or using a CF with counter, but if one of the calls results in exceptional completion of the composed future, the processing continues (e.g. with a retry). The other parallel operation handlers are not stopped, though. > {{BaseDistributionInterceptor.remoteGet}} shouldn't be called in parallel because it does not even synchronize regular successful invocations. > A problem like this caused failures in {{GetAllCommandStressTest}}, and the issue was addressed for {{GetAllCommand}} in ISPN-7884. -- 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 November 2019