July 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9372) Replace 2LC's XaTransactionImpl with impl from commons

by Radim Vansa (JIRA)

Radim Vansa created ISPN-9372: --------------------------------- Summary: Replace 2LC's XaTransactionImpl with impl from commons Key: ISPN-9372 URL: https://issues.jboss.org/browse/ISPN-9372 Project: Infinispan Issue Type: Task Components: Hibernate Cache Affects Versions: 9.3.0.Final Reporter: Radim Vansa Assignee: Radim Vansa Fix For: 9.4.0.Final https://hibernate.atlassian.net/browse/HHH-10164 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9371) Allow passing properties to RocksDB

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-9371: ------------------------------------- Summary: Allow passing properties to RocksDB Key: ISPN-9371 URL: https://issues.jboss.org/browse/ISPN-9371 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Affects Versions: 9.3.0.Final Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.4.0.Beta1 The org.rocksdb.DBOptions#getDBOptionsFromProps(java.util.Properties) method allows passing string-based properties for tuning RocksDB. We should pass through any such custom properties. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9364) Add support for 8.3, 8.4 and 8.5 schemas to the parsers

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9364?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9364: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add support for 8.3, 8.4 and 8.5 schemas to the parsers > ------------------------------------------------------- > > Key: ISPN-9364 > URL: https://issues.jboss.org/browse/ISPN-9364 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core, Server > Affects Versions: 9.3.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9350) Un-hardcode parser schema from tests

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9350?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9350: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Un-hardcode parser schema from tests > ------------------------------------ > > Key: ISPN-9350 > URL: https://issues.jboss.org/browse/ISPN-9350 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Test Suite - Core, Test Suite - Server > Affects Versions: 9.3.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Alpha1 > > > Many parser tests hardcode the schemas. This makes upgrading the schema versions cumbersome as it needs code changes. > Additionally, the server extensions also hardcode the versions. We should introduce something similar to ISPN-8952 to make the parsers dynamic -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9364) Add support for 8.3, 8.4 and 8.5 schemas to the parsers

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9364?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9364: ------------------------------- Status: Open (was: New) > Add support for 8.3, 8.4 and 8.5 schemas to the parsers > ------------------------------------------------------- > > Key: ISPN-9364 > URL: https://issues.jboss.org/browse/ISPN-9364 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core, Server > Affects Versions: 9.3.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9364) Add support for 8.3, 8.4 and 8.5 schemas to the parsers

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9364?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9364: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6128 > Add support for 8.3, 8.4 and 8.5 schemas to the parsers > ------------------------------------------------------- > > Key: ISPN-9364 > URL: https://issues.jboss.org/browse/ISPN-9364 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core, Server > Affects Versions: 9.3.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9362) Break cycles in exception stack traces

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9362?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9362: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.3.1.Final Resolution: Done > Break cycles in exception stack traces > -------------------------------------- > > Key: ISPN-9362 > URL: https://issues.jboss.org/browse/ISPN-9362 > Project: Infinispan > Issue Type: Task > Affects Versions: 9.3.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.4.0.Final, 9.3.1.Final > > > As most of the core became non-blocking, the exception stack traces became less relevant, because as the exception is re-thrown on multiple threads yet the stack trace only shows the initial thread. > ISPN-8893 improved this in some methods that are still blocking by catching an {{ExecutionException}}, adding it to the suppressed list of the cause, and rethrowing the cause. However, cycles in the exception trace is not properly supported by all loggers, e.g. {{logback}} only has a fix in the not yet released version 1.3.0. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9370) Always consult CacheLoader if entry is not in data container

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9370?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9370: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/6146, https://github.com/infinispan/infinispan/pull/6148 > Always consult CacheLoader if entry is not in data container > ------------------------------------------------------------ > > Key: ISPN-9370 > URL: https://issues.jboss.org/browse/ISPN-9370 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Alpha1, 9.3.1.Final > > > Currently we do not query the underlying persistence layer when an entry was found to be expired in memory. However it makes sense to query a CacheLoader (that is that it doesn't implement CacheStore) even when an entry is expired. This allows for users to configure a CacheLoader that always returns non null and the cache will never return null. > Please see https://github.com/infinispan/infinispan/pull/6071 more information -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9293) Convert Set<Integer> places to IntSet where appropriate

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9293?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9293: -------------------------------- Fix Version/s: 9.3.1.Final > Convert Set<Integer> places to IntSet where appropriate > ------------------------------------------------------- > > Key: ISPN-9293 > URL: https://issues.jboss.org/browse/ISPN-9293 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Alpha1, 9.4.0.Final, 9.3.1.Final > > > The IntSet class was introduced a while back. It was used instead of Set<Integer> if possible. This has some benefits with storage and network overhead. There are quite a few places that are not using the new IntSet. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9293) Convert Set<Integer> places to IntSet where appropriate

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9293?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9293: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6070, https://github.com/infinispan/infinispan/pull/6147 (was: https://github.com/infinispan/infinispan/pull/6070) > Convert Set<Integer> places to IntSet where appropriate > ------------------------------------------------------- > > Key: ISPN-9293 > URL: https://issues.jboss.org/browse/ISPN-9293 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Alpha1, 9.4.0.Final, 9.3.1.Final > > > The IntSet class was introduced a while back. It was used instead of Set<Integer> if possible. This has some benefits with storage and network overhead. There are quite a few places that are not using the new IntSet. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 July 2018