October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8112) Remove QueryKnownClasses

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8112?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8112: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Remove QueryKnownClasses > ------------------------ > > Key: ISPN-8112 > URL: https://issues.jboss.org/browse/ISPN-8112 > Project: Infinispan > Issue Type: Sub-task > Components: Embedded Querying > Reporter: Radim Vansa > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8491) Add streaming variant of off heap to not create byte[] instances

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8491?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8491: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Add streaming variant of off heap to not create byte[] instances > ---------------------------------------------------------------- > > Key: ISPN-8491 > URL: https://issues.jboss.org/browse/ISPN-8491 > Project: Infinispan > Issue Type: Sub-task > Components: Off Heap > Reporter: Will Burns > Priority: Major > Fix For: 10.0.1.Final > > > Currently off heap has to create a byte[] to copy memory from off heap. This is a waste of CPU and memory to do so. Instead we should have a streaming variant Output that the GlobalMarshaller can use that doesn't need all of this unnecessary copying. Unfortunately GlobalMarshaller is currently internally hard coded to require the usage of byte[] so we would have to tweak some code there as well to allow this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8241) Refactor RocksDB clearThreshold

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8241?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8241: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Refactor RocksDB clearThreshold > ------------------------------- > > Key: ISPN-8241 > URL: https://issues.jboss.org/browse/ISPN-8241 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.1.Final > > > Currently the RocksDB store utilises a "clearThreshold" to try to delete entries individually before deleting and re-initiating the database. We should deprecate this threshold and always delete/reinit the database. > Currently when deleting the database, we utilise Util.recursiveFileRemove which does not confirm that the file has actually been deleted. Instead, we should provide a nio based implementation instead, similar to the one stated [here|https://stackoverflow.com/questions/779519/delete-directories-recurs...]. This has the advantage that an IOException is thrown by java.nio.file.Files::delete -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8303) Cassandra Cache Store: Upgrade to latest Cassandra stable release 3.0.14

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8303?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8303: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Cassandra Cache Store: Upgrade to latest Cassandra stable release 3.0.14 > ------------------------------------------------------------------------ > > Key: ISPN-8303 > URL: https://issues.jboss.org/browse/ISPN-8303 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Reporter: Andrea Cosentino > Assignee: Andrea Cosentino > Priority: Major > Fix For: 10.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8242) Utilise Column Families for expiration

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8242?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8242: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Utilise Column Families for expiration > -------------------------------------- > > Key: ISPN-8242 > URL: https://issues.jboss.org/browse/ISPN-8242 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: Will Burns > Priority: Major > Fix For: 10.0.1.Final > > > Currently we utilise two separate databases for the actual data being stored and an expiration queue. Instead we should utilise [Column Families|https://github.com/facebook/rocksdb/wiki/Column-Families] as these allow for atomic updates across columns. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8324) Cache listener receives CacheEntriesEvictedEvent for entries irrespective of filter

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8324?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8324: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Cache listener receives CacheEntriesEvictedEvent for entries irrespective of filter > ----------------------------------------------------------------------------------- > > Key: ISPN-8324 > URL: https://issues.jboss.org/browse/ISPN-8324 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 9.1.1.Final > Reporter: Paul Ferraro > Priority: Major > Fix For: 10.0.1.Final > > Attachments: Test.java > > > If a cache registers a listener using a KeyFilter, should not receive CacheEntriesEvictedEvents for entries that do not honor the filter. See attached reproducer. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8260) Add user guide section for the deployment of analyzers with Ickle

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8260?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8260: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Add user guide section for the deployment of analyzers with Ickle > ----------------------------------------------------------------- > > Key: ISPN-8260 > URL: https://issues.jboss.org/browse/ISPN-8260 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 9.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8356) Embedded distribution names are confusing

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8356?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8356: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Embedded distribution names are confusing > ----------------------------------------- > > Key: ISPN-8356 > URL: https://issues.jboss.org/browse/ISPN-8356 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 9.1.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.1.Final > > > The binary distribution names for embedded libraries are confusing: > I propose the following names > > - infinispan-${version}-all.zip -> infinispan-embedded-${version}-all.zip > - infinispan-${version}-minimal.zip -> infinispan-embedded-${version}-minimal.zip > - infinispan-${version}-remote.zip -> infinispan-remote-${version}.zip > The website labelling needs to be modified accordingly too -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8441) The module spec used by server config of indexed-entities/indexed-entity and modules/module accepts only deployments

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8441?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8441: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > The module spec used by server config of indexed-entities/indexed-entity and modules/module accepts only deployments > -------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-8441 > URL: https://issues.jboss.org/browse/ISPN-8441 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 9.1.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > > The module name must start with "deployment." due to the use ServiceModuleLoader.moduleServiceName() method to resolve a service name from a module name. This only knows how to handle deployments from 'deployment' dir, regular modules from the 'modules' dir are not handled. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8453) Commit should fail if cache is in degraded mode

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8453?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8453: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Commit should fail if cache is in degraded mode > ----------------------------------------------- > > Key: ISPN-8453 > URL: https://issues.jboss.org/browse/ISPN-8453 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.9.Final, 8.2.8.Final, 9.1.2.Final, 9.2.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.1.Final > > > When the originator receives a {{CacheNotFoundResponse}} and the cache is in degraded mode, the transaction is marked as partially completed, but the commit completes successfully. > I believe that is not correct, because the originator could crash after the commit but before the merge, and in that case the transaction will not be applied on all the owners. The transaction manager will ignore any commit exception in {{NON_XA}}/{{useSynchronization}} mode, but at least in {{FULL_XA}}/{{NON_DURABLE_XA}} mode we can signal to the user that the transaction may be lost. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2019