July 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12073) Bring Infinispan SB Starter into Infinspan Release Lifecycle

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12073?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12073: ------------------------------- Fix Version/s: 12.0.0.Dev01 > Bring Infinispan SB Starter into Infinspan Release Lifecycle > ------------------------------------------------------------- > > Key: ISPN-12073 > URL: https://issues.redhat.com/browse/ISPN-12073 > Project: Infinispan > Issue Type: Task > Components: Spring Integration > Affects Versions: 11.0.1.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 12.0.0.Dev01 > > > Put the infinispan sb starter -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12073) Bring Infinispan SB Starter into Infinspan Release Lifecycle

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12073?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12073: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8527 > Bring Infinispan SB Starter into Infinspan Release Lifecycle > ------------------------------------------------------------- > > Key: ISPN-12073 > URL: https://issues.redhat.com/browse/ISPN-12073 > Project: Infinispan > Issue Type: Task > Components: Spring Integration > Affects Versions: 11.0.1.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Put the infinispan sb starter -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12123) HotRod per cache configuration in SB Starter

by Katia Aresti (Jira)

Katia Aresti created ISPN-12123: ----------------------------------- Summary: HotRod per cache configuration in SB Starter Key: ISPN-12123 URL: https://issues.redhat.com/browse/ISPN-12123 Project: Infinispan Issue Type: Feature Request Components: Spring Integration Affects Versions: 11.0.1.Final Reporter: Katia Aresti Assignee: Katia Aresti Make the Spring boot starter configuration upgraded to use the per cache configuration in the hotrod client with spring application.properties -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12122) Remote Store should check media types to determine segmentation support

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12122?page=com.atlassian.jira.plugi... ] Work on ISPN-12122 started by Will Burns. ----------------------------------------- > Remote Store should check media types to determine segmentation support > ----------------------------------------------------------------------- > > Key: ISPN-12122 > URL: https://issues.redhat.com/browse/ISPN-12122 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final > > > The RemoteStore today "supports" segmentation but it doesn't work properly unless a very specific combination of configuration settings are correct (key media type matches, raw values, marshaller etc). > We need to add in runtime checks and do the appropriate thing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12122) Remote Store should check media types to determine segmentation support

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12122?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12122: ------------------------------ Status: Open (was: New) > Remote Store should check media types to determine segmentation support > ----------------------------------------------------------------------- > > Key: ISPN-12122 > URL: https://issues.redhat.com/browse/ISPN-12122 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Will Burns > Priority: Major > Fix For: 12.0.0.Final > > > The RemoteStore today "supports" segmentation but it doesn't work properly unless a very specific combination of configuration settings are correct (key media type matches, raw values, marshaller etc). > We need to add in runtime checks and do the appropriate thing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12122) Remote Store should check media types to determine segmentation support

by Will Burns (Jira)

Will Burns created ISPN-12122: --------------------------------- Summary: Remote Store should check media types to determine segmentation support Key: ISPN-12122 URL: https://issues.redhat.com/browse/ISPN-12122 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Reporter: Will Burns Fix For: 12.0.0.Final The RemoteStore today "supports" segmentation but it doesn't work properly unless a very specific combination of configuration settings are correct (key media type matches, raw values, marshaller etc). We need to add in runtime checks and do the appropriate thing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11992) Convert RemoteStore to use new SPI

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11992?page=com.atlassian.jira.plugi... ] Will Burns reassigned ISPN-11992: --------------------------------- Assignee: Will Burns > Convert RemoteStore to use new SPI > ---------------------------------- > > Key: ISPN-11992 > URL: https://issues.redhat.com/browse/ISPN-11992 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final, 11.0.2.Final > > > The RemoteStore already uses a non blocking client. We should convert it to the new SPI to utilize this. > We also need to add in a check for the old server to see how many segments it has. If the number is different than the current server we need to disable the segmentation characteristic and instead do the costlier iteration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11992) Convert RemoteStore to use new SPI

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11992?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11992: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/8552 (was: https://issues.redhat.com/browse/ISPN-12043) > Convert RemoteStore to use new SPI > ---------------------------------- > > Key: ISPN-11992 > URL: https://issues.redhat.com/browse/ISPN-11992 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Will Burns > Priority: Major > Fix For: 12.0.0.Final, 11.0.2.Final > > > The RemoteStore already uses a non blocking client. We should convert it to the new SPI to utilize this. > We also need to add in a check for the old server to see how many segments it has. If the number is different than the current server we need to disable the segmentation characteristic and instead do the costlier iteration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11286) compute(...) is not working without any error message if expiration parameter is used

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11286?page=com.atlassian.jira.plugi... ] Tristan Tarrant reassigned ISPN-11286: -------------------------------------- Assignee: Will Burns > compute(...) is not working without any error message if expiration parameter is used > ------------------------------------------------------------------------------------- > > Key: ISPN-11286 > URL: https://issues.redhat.com/browse/ISPN-11286 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > Attachments: Book.java, LibraryManager.java > > > If the compute operation is used with expiration parameters the value is not applied without any error message! > compute() without expiration or a put() with expiration will work correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11336) Infinispan BOM should only have dependency management

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11336?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11336: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Infinispan BOM should only have dependency management > ----------------------------------------------------- > > Key: ISPN-11336 > URL: https://issues.redhat.com/browse/ISPN-11336 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 10.1.2.Final > Reporter: Stéphane Nicoll > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.0.0.Dev01 > > > The BOM has a {{pluginManagement}} section that's a bit misleading since Maven isn't going to do anything with it. > It is also invalid at the moment per the following: > {code:xml} > <plugin> > <groupId>org.infinispan.maven-plugins</groupId> > <artifactId>protocol-parser-generator</artifactId> > <version>${version.infinispan.maven-plugins}</version> > </plugin> > {code} > This artifact does not seem to be published anymore. Using the BOM with resolution leads to > {noformat} > [WARNING] The POM for org.infinispan:infinispan-protocol-parser-generator-maven-plugin:jar:10.1.1.Final is missing, no dependency information available > [WARNING] Failed to retrieve plugin descriptor for org.infinispan:infinispan-protocol-parser-generator-maven-plugin:10.1.1.Final: Plugin org.infinispan:infinispan-protocol-parser-generator-maven-plugin:10.1.1.Final or one of its dependencies could not be resolved: Failure to find org.infinispan:infinispan-protocol-parser-generator-maven-plugin:jar:10.1.1.Final in https://repo.spring.io/milestone was cached in the local repository, resolution will not be reattempted until the update interval of spring-milestones has elapsed or updates are forced > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2020