April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2634) Implement cross-site replication based on I-RAC (Reliably Asynchronous Clustering)

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-2634?page=com.atlassian.jira.plugin... ] Work on ISPN-2634 started by Pedro Ruivo. ----------------------------------------- > Implement cross-site replication based on I-RAC (Reliably Asynchronous Clustering) > ---------------------------------------------------------------------------------- > > Key: ISPN-2634 > URL: https://issues.redhat.com/browse/ISPN-2634 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Reporter: Mircea Markus > Assignee: Pedro Ruivo > Priority: Major > > As described here: https://community.jboss.org/wiki/RAC > Newer version here? > https://github.com/infinispan/infinispan-designs/blob/master/RAC:-Reliabl... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11615) Replace internal metadata class

by Pedro Ruivo (Jira)

Pedro Ruivo created ISPN-11615: ---------------------------------- Summary: Replace internal metadata class Key: ISPN-11615 URL: https://issues.redhat.com/browse/ISPN-11615 Project: Infinispan Issue Type: Sub-task Affects Versions: 11.0.0.Dev03 Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 11.0.0.Dev04 Replace {{MetaParamsInternalMetadata}} with a more compacted class to store internal metadata. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11614) PersistenceMarshaller should utilise an independent SerializationContext for user types

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-11614: ----------------------------------- Summary: PersistenceMarshaller should utilise an independent SerializationContext for user types Key: ISPN-11614 URL: https://issues.redhat.com/browse/ISPN-11614 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 11.0.0.Dev03, 10.1.5.Final Reporter: Ryan Emerson Assignee: Ryan Emerson If a user configures a SerializationContextInitializer it is currently registered to the same SerializationContext as the persistent internal types. This means that it is possible for a user to reference internal protobuf message types in their .proto files. We should utilise a seperate SerializationContext to ensure that these types are truly indepdenent. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11612) Update embedded wtih maven repository details

by Donald Naro (Jira)

Donald Naro created ISPN-11612: ---------------------------------- Summary: Update embedded wtih maven repository details Key: ISPN-11612 URL: https://issues.redhat.com/browse/ISPN-11612 Project: Infinispan Issue Type: Enhancement Reporter: Donald Naro Assignee: Donald Naro Need to modify the docs for embedded to clarify about the maven repository setup. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11426) Add UUID to core SerializationContexts

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11426?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11426: -------------------------------- Description: Currently we only register a ProtoStream marshaller for java.util.UUID in the server as they are required for the event logger, however this will also be required by core for `MultiClusterEventCommand` and `ClusterEvent`. It's not possible to register a class in multiple contexts when utilising a TypeId, therefore in order to avoid having to provide a TypeId for UUIDs in both core and server, we should register this in the core's persistence initializers. A flip-side to this is that it will also mean that UUIDs will be supported by default in embedded mode. (was: Currently we only register a ProtoStream marshaller for java.util.UUID in the server as they are required for the event logger, however we should register this in the common's initializers as it is a common requirement for users to use UUID as keys in a cache.) > Add UUID to core SerializationContexts > -------------------------------------- > > Key: ISPN-11426 > URL: https://issues.redhat.com/browse/ISPN-11426 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > Currently we only register a ProtoStream marshaller for java.util.UUID in the server as they are required for the event logger, however this will also be required by core for `MultiClusterEventCommand` and `ClusterEvent`. It's not possible to register a class in multiple contexts when utilising a TypeId, therefore in order to avoid having to provide a TypeId for UUIDs in both core and server, we should register this in the core's persistence initializers. A flip-side to this is that it will also mean that UUIDs will be supported by default in embedded mode. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11426) Add UUID to core SerializationContexts

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11426?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11426: -------------------------------- Summary: Add UUID to core SerializationContexts (was: Add UUID to commons SerializationContexts) > Add UUID to core SerializationContexts > -------------------------------------- > > Key: ISPN-11426 > URL: https://issues.redhat.com/browse/ISPN-11426 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > Currently we only register a ProtoStream marshaller for java.util.UUID in the server as they are required for the event logger, however we should register this in the common's initializers as it is a common requirement for users to use UUID as keys in a cache. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11611) Add internal metadata to persistence

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11611?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11611: ------------------------------- Status: Open (was: New) > Add internal metadata to persistence > ------------------------------------ > > Key: ISPN-11611 > URL: https://issues.redhat.com/browse/ISPN-11611 > Project: Infinispan > Issue Type: Sub-task > Affects Versions: 11.0.0.Dev03 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.Dev04 > > > The final step is to add the internal metadata to the persistence layer. This includes changing the cache stores to properly store it. > REST and HotRod won't support internal metadata otherwise, it has to be exposed in the public API. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11611) Add internal metadata to persistence

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11611?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11611: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8180 > Add internal metadata to persistence > ------------------------------------ > > Key: ISPN-11611 > URL: https://issues.redhat.com/browse/ISPN-11611 > Project: Infinispan > Issue Type: Sub-task > Affects Versions: 11.0.0.Dev03 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.Dev04 > > > The final step is to add the internal metadata to the persistence layer. This includes changing the cache stores to properly store it. > REST and HotRod won't support internal metadata otherwise, it has to be exposed in the public API. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11611) Add internal metadata to persistence

by Pedro Ruivo (Jira)

Pedro Ruivo created ISPN-11611: ---------------------------------- Summary: Add internal metadata to persistence Key: ISPN-11611 URL: https://issues.redhat.com/browse/ISPN-11611 Project: Infinispan Issue Type: Sub-task Affects Versions: 11.0.0.Dev03 Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 11.0.0.Dev04 The final step is to add the internal metadata to the persistence layer. This includes changing the cache stores to properly store it. REST and HotRod won't support internal metadata otherwise, it has to be exposed in the public API. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10457) Convert bulk blocking stream operations to publisher

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-10457?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-10457: ------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Convert bulk blocking stream operations to publisher > ---------------------------------------------------- > > Key: ISPN-10457 > URL: https://issues.redhat.com/browse/ISPN-10457 > Project: Infinispan > Issue Type: Enhancement > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > We now have the non blocking DistributedPublisher for single response values. We should use this or some other public API instead of the blocking bulk operations. For example size method is blocking and we should use the appropriate one instead. Methods using iteration over entrySet or keySet cannot yet be converted unfortunately. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2020