May 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11842) Upgrade to 2.3 Spring-Boot and Spring dependencies

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11842?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11842: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8330 > Upgrade to 2.3 Spring-Boot and Spring dependencies > -------------------------------------------------- > > Key: ISPN-11842 > URL: https://issues.redhat.com/browse/ISPN-11842 > Project: Infinispan > Issue Type: Component Upgrade > Components: Spring Integration > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Spring-Boot 2.3 has been released > Align to the latest versions > Spring Security 5.3.2.RELEASE > Spring Integration 5.3.0.RELEASE > Spring Session 2.3.0.RELEASE -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11842) Upgrade to 2.3 Spring-Boot and Spring dependencies

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11842?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11842: -------------------------------- Description: Spring-Boot 2.3 has been released Align to the latest versions Spring Security 5.3.2.RELEASE Spring Integration 5.3.0.RELEASE Spring Session 2.3.0.RELEASE was: Spring-Boot 2.3 has been released Align to the latest versions > Upgrade to 2.3 Spring-Boot and Spring dependencies > -------------------------------------------------- > > Key: ISPN-11842 > URL: https://issues.redhat.com/browse/ISPN-11842 > Project: Infinispan > Issue Type: Component Upgrade > Components: Spring Integration > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Spring-Boot 2.3 has been released > Align to the latest versions > Spring Security 5.3.2.RELEASE > Spring Integration 5.3.0.RELEASE > Spring Session 2.3.0.RELEASE -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11842) Upgrade to 2.3 Spring-Boot and Spring dependencies

by Katia Aresti (Jira)

Katia Aresti created ISPN-11842: ----------------------------------- Summary: Upgrade to 2.3 Spring-Boot and Spring dependencies Key: ISPN-11842 URL: https://issues.redhat.com/browse/ISPN-11842 Project: Infinispan Issue Type: Component Upgrade Components: Spring Integration Reporter: Katia Aresti Assignee: Katia Aresti Spring-Boot 2.3 has been released Align to the latest versions -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11801) Upgrade to 2.2.7.RELEASE and 11

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11801?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11801: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to 2.2.7.RELEASE and 11 > ------------------------------- > > Key: ISPN-11801 > URL: https://issues.redhat.com/browse/ISPN-11801 > Project: Infinispan > Issue Type: Component Upgrade > Components: Spring Integration > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Optional > > Upgrade SB starter to the latest SB 2.2.7.RELEASE and 11 dev5 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11802) Create SPI for Cross-Site Replication conflict resolution

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11802?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11802: ------------------------------- Sprint: DataGrid Sprint #44 > Create SPI for Cross-Site Replication conflict resolution > --------------------------------------------------------- > > Key: ISPN-11802 > URL: https://issues.redhat.com/browse/ISPN-11802 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > > A conflict happens if 2 sites try to update the same key (put/remove) concurrently. > With async Cross-Site Replication (aka IRAC) when a conflict is detected, we use the site name to pick the winning update. > h2. Interface > {code:java} > interface ABC<V> { // or concrete class > String site(); //the site name which wrote this value > V value(); // the value. can be null if the key was removed > Metadata metadata(); //can be null > } > interface Resolve<K, V> { > ABC<V> resolve(K key, ABC<V> entry1, ABC<V> entry2); > } > {code} > h2. Configuration > Set the class name to use. Can be a {{Class}} object (as shown above) or a {{String}} with the class name. > For server mode, you need to add your jar with the classes required to {{server/lib}}. > The configuration fails to validate if the conflict resolution class is set with {{SYNC}} strategy. > {code:java} > ConfigurationBuilder.sites().addBackup() > .site("S") > .strategy(BackupConfiguration.BackupStrategy.ASYNC) > .conflictResolution(MyResover.class); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11802) Create SPI for Cross-Site Replication conflict resolution

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11802?page=com.atlassian.jira.plugi... ] Work on ISPN-11802 started by Pedro Ruivo. ------------------------------------------ > Create SPI for Cross-Site Replication conflict resolution > --------------------------------------------------------- > > Key: ISPN-11802 > URL: https://issues.redhat.com/browse/ISPN-11802 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > > A conflict happens if 2 sites try to update the same key (put/remove) concurrently. > With async Cross-Site Replication (aka IRAC) when a conflict is detected, we use the site name to pick the winning update. > h2. Interface > {code:java} > interface ABC<V> { // or concrete class > String site(); //the site name which wrote this value > V value(); // the value. can be null if the key was removed > Metadata metadata(); //can be null > } > interface Resolve<K, V> { > ABC<V> resolve(K key, ABC<V> entry1, ABC<V> entry2); > } > {code} > h2. Configuration > Set the class name to use. Can be a {{Class}} object (as shown above) or a {{String}} with the class name. > For server mode, you need to add your jar with the classes required to {{server/lib}}. > The configuration fails to validate if the conflict resolution class is set with {{SYNC}} strategy. > {code:java} > ConfigurationBuilder.sites().addBackup() > .site("S") > .strategy(BackupConfiguration.BackupStrategy.ASYNC) > .conflictResolution(MyResover.class); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11802) Create SPI for Cross-Site Replication conflict resolution

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11802?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11802: ------------------------------- Status: Open (was: New) > Create SPI for Cross-Site Replication conflict resolution > --------------------------------------------------------- > > Key: ISPN-11802 > URL: https://issues.redhat.com/browse/ISPN-11802 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > > A conflict happens if 2 sites try to update the same key (put/remove) concurrently. > With async Cross-Site Replication (aka IRAC) when a conflict is detected, we use the site name to pick the winning update. > h2. Interface > {code:java} > interface ABC<V> { // or concrete class > String site(); //the site name which wrote this value > V value(); // the value. can be null if the key was removed > Metadata metadata(); //can be null > } > interface Resolve<K, V> { > ABC<V> resolve(K key, ABC<V> entry1, ABC<V> entry2); > } > {code} > h2. Configuration > Set the class name to use. Can be a {{Class}} object (as shown above) or a {{String}} with the class name. > For server mode, you need to add your jar with the classes required to {{server/lib}}. > The configuration fails to validate if the conflict resolution class is set with {{SYNC}} strategy. > {code:java} > ConfigurationBuilder.sites().addBackup() > .site("S") > .strategy(BackupConfiguration.BackupStrategy.ASYNC) > .conflictResolution(MyResover.class); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11803) Move Optimistic Transaction versions to PrivateMetadata

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11803?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11803: ------------------------------- Sprint: DataGrid Sprint #44 > Move Optimistic Transaction versions to PrivateMetadata > ------------------------------------------------------- > > Key: ISPN-11803 > URL: https://issues.redhat.com/browse/ISPN-11803 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > > The versions used by the Optimistic Transactions to detect write-skew should be stored in the {{PrivateMetadata}} class instead of being exposed to users via {{Metadata#version(}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11803) Move Optimistic Transaction versions to PrivateMetadata

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11803?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11803: ------------------------------- Status: Open (was: New) > Move Optimistic Transaction versions to PrivateMetadata > ------------------------------------------------------- > > Key: ISPN-11803 > URL: https://issues.redhat.com/browse/ISPN-11803 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > > The versions used by the Optimistic Transactions to detect write-skew should be stored in the {{PrivateMetadata}} class instead of being exposed to users via {{Metadata#version(}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11803) Move Optimistic Transaction versions to PrivateMetadata

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11803?page=com.atlassian.jira.plugi... ] Work on ISPN-11803 started by Pedro Ruivo. ------------------------------------------ > Move Optimistic Transaction versions to PrivateMetadata > ------------------------------------------------------- > > Key: ISPN-11803 > URL: https://issues.redhat.com/browse/ISPN-11803 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > > The versions used by the Optimistic Transactions to detect write-skew should be stored in the {{PrivateMetadata}} class instead of being exposed to users via {{Metadata#version(}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2020