July 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9353) CacheMgmtInterceptor doesn't handle exceptions in GetAllCommand results

by Dan Berindei (JIRA)

Dan Berindei created ISPN-9353: ---------------------------------- Summary: CacheMgmtInterceptor doesn't handle exceptions in GetAllCommand results Key: ISPN-9353 URL: https://issues.jboss.org/browse/ISPN-9353 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.3.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9353) CacheMgmtInterceptor doesn't handle exceptions in GetAllCommand results

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9353?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9353: ------------------------------- Status: Open (was: New) > CacheMgmtInterceptor doesn't handle exceptions in GetAllCommand results > ----------------------------------------------------------------------- > > Key: ISPN-9353 > URL: https://issues.jboss.org/browse/ISPN-9353 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.3.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9301) Add read timeout configuration to the Spring Cache provider

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9301?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9301: ---------------------------------- Fix Version/s: 9.4.0.Alpha1 9.4.0.Final > Add read timeout configuration to the Spring Cache provider > ----------------------------------------------------------- > > Key: ISPN-9301 > URL: https://issues.jboss.org/browse/ISPN-9301 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod, Spring Integration > Affects Versions: 9.2.4.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Alpha1, 9.4.0.Final > > > The Spring Cache provider has no distinction between sync and async calls. In a cache scenario with fail-fast semantics it is desirable to fail a read operation when it doesn't complete within a specified timeout. > We should add a configuration property which implements this -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9301) Add read timeout configuration to the Spring Cache provider

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9301?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9301: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6134 > Add read timeout configuration to the Spring Cache provider > ----------------------------------------------------------- > > Key: ISPN-9301 > URL: https://issues.jboss.org/browse/ISPN-9301 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod, Spring Integration > Affects Versions: 9.2.4.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Alpha1, 9.4.0.Final > > > The Spring Cache provider has no distinction between sync and async calls. In a cache scenario with fail-fast semantics it is desirable to fail a read operation when it doesn't complete within a specified timeout. > We should add a configuration property which implements this -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9072) Document Protobuf annotated collection null set callbacks

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-9072?page=com.atlassian.jira.plugin.... ] Adrian Nistor edited comment on ISPN-9072 at 7/9/18 5:01 AM: ------------------------------------------------------------- The issue is solved in protostream, to be included in next 4.3 release which will be used by ISPN 9.4. The fix consists of always setting empty collections instead of nulls. This has a slight chance to break existing code and the idea of introducing an attribute in ProtoField annotation was intended to avoid that, but given the limited potential impact I deferred that for now. was (Author: anistor): The issue is solved protostream, to be included in next 4.3 release which will be used by ISPN 9.4. The fix consists of always setting empty collections instead of nulls. This has a slight chance to break existing code and the idea of introducing an attribute in ProtoField annotation was intended to avoid that, but given the limited potential impact I deferred that for now. > Document Protobuf annotated collection null set callbacks > --------------------------------------------------------- > > Key: ISPN-9072 > URL: https://issues.jboss.org/browse/ISPN-9072 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Affects Versions: 9.2.1.Final > Reporter: Galder Zamarreño > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > > When using collection fields in Protobuf annotated classes, empty collections are marshalled into the same value as {{null}}, because Protobuf only has repeated fields and no fields is represented as {{null}}. > This means that if you have an entity with an empty collection, when it's deserialized the collection will be null. This can be confusing for users and should be documented. > [~anistor] had some ideas on how to improve this: > {code} > <anistor> I'm thinking of a way to make this easier for users that > would prefer an empty collection being set instead of a > null. would be possible by adding a new attribute for this in > @ProtoField anotation > > that'd be more predictable > <anistor> would still not give you at deserializtion what was written > during serialization. we do not have a null marker > <anistor> it would just give you an empty collection if you prefer > <anistor> instead of null > > that option should be enabled by default > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9072) Document Protobuf annotated collection null set callbacks

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-9072?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-9072: ------------------------------------- The issue is solved protostream, to be included in next 4.3 release which will be used by ISPN 9.4. The fix consists of always setting empty collections instead of nulls. This has a slight chance to break existing code and the idea of introducing an attribute in ProtoField annotation was intended to avoid that, but given the limited potential impact I deferred that for now. > Document Protobuf annotated collection null set callbacks > --------------------------------------------------------- > > Key: ISPN-9072 > URL: https://issues.jboss.org/browse/ISPN-9072 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Affects Versions: 9.2.1.Final > Reporter: Galder Zamarreño > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > > When using collection fields in Protobuf annotated classes, empty collections are marshalled into the same value as {{null}}, because Protobuf only has repeated fields and no fields is represented as {{null}}. > This means that if you have an entity with an empty collection, when it's deserialized the collection will be null. This can be confusing for users and should be documented. > [~anistor] had some ideas on how to improve this: > {code} > <anistor> I'm thinking of a way to make this easier for users that > would prefer an empty collection being set instead of a > null. would be possible by adding a new attribute for this in > @ProtoField anotation > > that'd be more predictable > <anistor> would still not give you at deserializtion what was written > during serialization. we do not have a null marker > <anistor> it would just give you an empty collection if you prefer > <anistor> instead of null > > that option should be enabled by default > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-64) Annotation based marshallers should unmarshall empty repeatable fields as empty collections instead of null

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-64?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-64: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master > Annotation based marshallers should unmarshall empty repeatable fields as empty collections instead of null > ----------------------------------------------------------------------------------------------------------- > > Key: IPROTO-64 > URL: https://issues.jboss.org/browse/IPROTO-64 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 4.3.0.Alpha1, 4.3.0.Final > > > They are currently set to null but it would be more useful to set them to empty collections. > Protobuf does not have a representation for null or for empty/missing repeatable fields. Whether these are represented as null or empty collection in Java code is just a matter of convenience. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9254) Document Single Port

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-9254?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-9254: -------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6133 (was: https://github.com/infinispan/infinispan/pull/6035) > Document Single Port > -------------------- > > Key: ISPN-9254 > URL: https://issues.jboss.org/browse/ISPN-9254 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Sebastian Łaskawiec > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8756) Implement Single Port

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8756?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8756: -------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/5728, https://github.com/infinispan/infinispan/pull/6133 (was: https://github.com/infinispan/infinispan/pull/5728) > Implement Single Port > --------------------- > > Key: ISPN-8756 > URL: https://issues.jboss.org/browse/ISPN-8756 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > Design document: https://github.com/infinispan/infinispan-designs/blob/master/Single_port.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9352) Report cache read/write/remote stats also as nanoseconds

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9352?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9352: ---------------------------------- Status: Open (was: New) > Report cache read/write/remote stats also as nanoseconds > -------------------------------------------------------- > > Key: ISPN-9352 > URL: https://issues.jboss.org/browse/ISPN-9352 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Affects Versions: 9.3.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Alpha1, 9.4.0.Final > > > Add three new stats that report read/write/remove averages in nanoseconds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 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 2018