May 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3071) DefaultTwoWayKey2StringMapper should support native byte[] keys

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3071?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3071: ---------------------------------- Fix Version/s: 5.3.0.Beta1 > DefaultTwoWayKey2StringMapper should support native byte[] keys > --------------------------------------------------------------- > > Key: ISPN-3071 > URL: https://issues.jboss.org/browse/ISPN-3071 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.3.0.Beta1 > > > Since the introduction of ISPN-2281 we need to support byte[] keys as first-class citizens in the DefaultTwoWayKey2StringMapper -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3073) Remove deprecated configuration elements from default JGroups config

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3073: ------------------------------------- Summary: Remove deprecated configuration elements from default JGroups config Key: ISPN-3073 URL: https://issues.jboss.org/browse/ISPN-3073 Project: Infinispan Issue Type: Task Components: Server Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Minor Fix For: 5.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3072) Infinispan server extension should use a custom equivalence class for keys/values

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3072?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3072: ---------------------------------- Priority: Blocker (was: Major) > Infinispan server extension should use a custom equivalence class for keys/values > --------------------------------------------------------------------------------- > > Key: ISPN-3072 > URL: https://issues.jboss.org/browse/ISPN-3072 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 5.3.0.Beta1 > > > Without a custom equivalence class, HotRod servers can't find keys anymore -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3072) Infinispan server extension should use a custom equivalence class for keys/values

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3072: ------------------------------------- Summary: Infinispan server extension should use a custom equivalence class for keys/values Key: ISPN-3072 URL: https://issues.jboss.org/browse/ISPN-3072 Project: Infinispan Issue Type: Bug Components: Server Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.3.0.Beta1 Without a custom equivalence class, HotRod servers can't find keys anymore -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3071) DefaultTwoWayKey2StringMapper should support native byte[] keys

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3071: ------------------------------------- Summary: DefaultTwoWayKey2StringMapper should support native byte[] keys Key: ISPN-3071 URL: https://issues.jboss.org/browse/ISPN-3071 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Critical Since the introduction of ISPN-2281 we need to support byte[] keys as first-class citizens in the DefaultTwoWayKey2StringMapper -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3070) Server protocol tests should also test against loaders/stores

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3070: ------------------------------------- Summary: Server protocol tests should also test against loaders/stores Key: ISPN-3070 URL: https://issues.jboss.org/browse/ISPN-3070 Project: Infinispan Issue Type: Task Components: Loaders and Stores, Remote protocols, Test Suite Affects Versions: 5.3.0.Alpha1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.3.0.Final We need server tests which use loaders/stores -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2218) Create maven-only release script

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2218?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2218: -------------------------------- Assignee: Mircea Markus (was: Galder Zamarreño) > Create maven-only release script > -------------------------------- > > Key: ISPN-2218 > URL: https://issues.jboss.org/browse/ISPN-2218 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Fix For: 6.0.0.Final > > > Create a reduced version of release.py to do Maven-only releases. Make sure as much as code is shared with the existing release.py script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2974) DeltaAware based fine-grained replication corrupts cache data, if eviction is enabled

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2974?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2974: -------------------------------- Fix Version/s: 5.2.6.Final > DeltaAware based fine-grained replication corrupts cache data, if eviction is enabled > ------------------------------------------------------------------------------------- > > Key: ISPN-2974 > URL: https://issues.jboss.org/browse/ISPN-2974 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.1.Final, 5.2.5.Final > Reporter: Horia Chiorean > Assignee: Adrian Nistor > Priority: Critical > Labels: 5.2.x > Fix For: 5.2.6.Final, 5.3.0.Beta1 > > > When using a custom {{DeltaAware}} implementation in a cluster with 2 replicated nodes with eviction enabled, data transferred from one node (the writer) to the another (the reader) causes data stored on this node and evicted at the time of the change, to be rewritten with whatever the partial latest delta was. > In more detail: > * configure 2 nodes in replicated mode, with eviction enabled > * consider NodeA the writer and NodeB the reader > * NodeA inserts some data (custom entries) into the cache > * NodeB correctly receives via state transfer the initial data > * NodeA loads & partially updates some information about an entry which was not in the cache - was evicted previously > * NodeB receives the partial delta with the changes from NodeA, but *instead of merging* with whatever is stored in the persistent store, *replaces the entire entry in the cache*, leaving it in effect with "partial/corrupt information" > If eviction is not enabled, everything works as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2974) DeltaAware based fine-grained replication corrupts cache data, if eviction is enabled

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2974?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2974: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > DeltaAware based fine-grained replication corrupts cache data, if eviction is enabled > ------------------------------------------------------------------------------------- > > Key: ISPN-2974 > URL: https://issues.jboss.org/browse/ISPN-2974 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.1.Final, 5.2.5.Final > Reporter: Horia Chiorean > Assignee: Adrian Nistor > Priority: Critical > Labels: 5.2.x > Fix For: 5.2.6.Final, 5.3.0.Beta1 > > > When using a custom {{DeltaAware}} implementation in a cluster with 2 replicated nodes with eviction enabled, data transferred from one node (the writer) to the another (the reader) causes data stored on this node and evicted at the time of the change, to be rewritten with whatever the partial latest delta was. > In more detail: > * configure 2 nodes in replicated mode, with eviction enabled > * consider NodeA the writer and NodeB the reader > * NodeA inserts some data (custom entries) into the cache > * NodeB correctly receives via state transfer the initial data > * NodeA loads & partially updates some information about an entry which was not in the cache - was evicted previously > * NodeB receives the partial delta with the changes from NodeA, but *instead of merging* with whatever is stored in the persistent store, *replaces the entire entry in the cache*, leaving it in effect with "partial/corrupt information" > If eviction is not enabled, everything works as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2988) Invalid Transport.isCoordinator() usages in ClusteredActivationInterceptor and ClusteredCacheLoaderInterceptor in REPL mode

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2988?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2988: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Invalid Transport.isCoordinator() usages in ClusteredActivationInterceptor and ClusteredCacheLoaderInterceptor in REPL mode > --------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2988 > URL: https://issues.jboss.org/browse/ISPN-2988 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 5.2.x > Fix For: 5.2.6.Final, 5.3.0.Beta1 > > > Transport.isCoordinator() is used to determine if we are the primary owner but this usage is no longer valid since the introduction of asymmetric caches. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2013