July 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (IPROTO-12) Add support for 'oneof' in proto schema

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-12?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-12: -------------------------------- Fix Version/s: 4.0.0.Final > Add support for 'oneof' in proto schema > --------------------------------------- > > Key: IPROTO-12 > URL: https://issues.jboss.org/browse/IPROTO-12 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 3.1.0.Alpha1, 3.1.0.Final, 4.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-12) Add support for 'oneof' in proto schema

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-12?page=com.atlassian.jira.plugin.... ] Work on IPROTO-12 started by Adrian Nistor. ------------------------------------------- > Add support for 'oneof' in proto schema > --------------------------------------- > > Key: IPROTO-12 > URL: https://issues.jboss.org/browse/IPROTO-12 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 3.1.0.Alpha1, 3.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-12) Add support for 'oneof' in proto schema

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-12?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned IPROTO-12: ----------------------------------- Assignee: Adrian Nistor > Add support for 'oneof' in proto schema > --------------------------------------- > > Key: IPROTO-12 > URL: https://issues.jboss.org/browse/IPROTO-12 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 3.1.0.Alpha1, 3.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-12) Add support for 'oneof' in proto schema

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-12?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-12: -------------------------------- Status: Open (was: New) > Add support for 'oneof' in proto schema > --------------------------------------- > > Key: IPROTO-12 > URL: https://issues.jboss.org/browse/IPROTO-12 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Reporter: Adrian Nistor > Fix For: 3.1.0.Alpha1, 3.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-12) Add support for 'oneof' in proto schema

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-12?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-12: -------------------------------- Fix Version/s: 3.1.0.Alpha1 3.1.0.Final > Add support for 'oneof' in proto schema > --------------------------------------- > > Key: IPROTO-12 > URL: https://issues.jboss.org/browse/IPROTO-12 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Reporter: Adrian Nistor > Fix For: 3.1.0.Alpha1, 3.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-12) Add support for 'oneof' in proto schema

by Adrian Nistor (JIRA)

Adrian Nistor created IPROTO-12: ----------------------------------- Summary: Add support for 'oneof' in proto schema Key: IPROTO-12 URL: https://issues.jboss.org/browse/IPROTO-12 Project: Infinispan ProtoStream Issue Type: Feature Request Reporter: Adrian Nistor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-3835: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Index Update command is processed before the registry listener is triggered > --------------------------------------------------------------------------- > > Key: ISPN-3835 > URL: https://issues.jboss.org/browse/ISPN-3835 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Critical > Labels: 64QueryBlockers > Fix For: 9.0.0.Alpha4 > > > When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet. > Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event. > This leads to index update commands to be lost (with a stacktrace logged) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3344) Create a release script for ProtoStream library

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-3344?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-3344: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Create a release script for ProtoStream library > ----------------------------------------------- > > Key: ISPN-3344 > URL: https://issues.jboss.org/browse/ISPN-3344 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 6.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha4 > > > Need to add license information and a short README to the project. Also update the 'Cutting Infinispan Releases' document with relevant details for Protostream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3906) Do not place ProtobufValueWrapper instances in the cache

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-3906?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-3906: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Do not place ProtobufValueWrapper instances in the cache > -------------------------------------------------------- > > Key: ISPN-3906 > URL: https://issues.jboss.org/browse/ISPN-3906 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha4 > > > ProtobufValueWrapper is only needed in order to provide a classbridge so we can integrate with Hibernate Search. Still, we should not need to wrap the protobuf encoded byte array put in the cache with this class. It should only be created as a temporary wrapper just before we feed the data to Hibernate Search. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3918) Inconsistent view of the cache with putIfAbsent in a non-tx cache during state transfer

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-3918?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-3918: -------------------------------------- Fix Version/s: 9.0.0.Alpha4 (was: 9.0.0.Alpha3) > Inconsistent view of the cache with putIfAbsent in a non-tx cache during state transfer > --------------------------------------------------------------------------------------- > > Key: ISPN-3918 > URL: https://issues.jboss.org/browse/ISPN-3918 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Fix For: 9.0.0.Alpha4 > > Attachments: ntpiadjst.log.gz > > > In a non-tx cache, sometimes it's possible for a {{get(k)}} to return {{null}} even though a previous {{putIfAbsent(k, v)}} returned a non-null value and the only concurrent operations on the cache are concurrent putIfAbsent calls. > Say \[B, A, C] are the owners of k (C just joined) > 1. A starts a {{putIfAbsent(k, v1)}} command, sends it to B > 2. B forwards the command to A and C > 3. C writes {{k=v1}} > 4. C becomes the primary owner of k (owners are now \[C, A]) > 5. A/B see the new topology before committing and throw an outdatedTopologyException > 6. A retries the command, sends it to C > 7. C forwards the command to A, which writes {{k=v1}} > 8. C doesn't have to update the entry, returns null > If, between steps 3 and 7, another thread on A starts a {{putIfAbsent(k, v2)}} command, the command will fail and return {{v1}} (because the primary owner already has a value). However, a subsequent {{get(k)}} command will return {{null}}, because A is an owner and doesn't have the value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2016