November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10418) java.lang.UnsupportedOperationException: FieldDescriptor.getDefaultValue() called on an embedded message field (only scalars can have a default value)

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10418?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10418: ----------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > java.lang.UnsupportedOperationException: FieldDescriptor.getDefaultValue() called on an embedded message field (only scalars can have a default value) > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-10418 > URL: https://issues.jboss.org/browse/ISPN-10418 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 10.0.0.Beta4 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.Beta5 > > > This started to happen after upgrading to protostream 4.3 which introduces some asserts in FieldDescriptor.getDefaultValue() with the recently fixed IPROTO-80. > This happens mainly due to IndexingTagHandler.indexMissingFields calling getDefaultValue() regardless of the type. > {code} > org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=686 returned server error (status=0x85): org.infinispan.remoting.RemoteException: ISPN000217: Received exception from RemoteContinuousQueryTest-NodeD-22902, see cause for remote stack trace > org.hibernate.search.bridge.BridgeException: Exception while calling bridge#set > entity class: org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper > field bridge: org.infinispan.query.remote.impl.indexing.ProtobufValueWrapperFieldBridge@1b9bf39c > java.lang.UnsupportedOperationException: FieldDescriptor.getDefaultValue() called on an embedded message field (only scalars can have a default value). > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:340) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:177) > at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:138) > at org.infinispan.client.hotrod.impl.transport.netty.HintedReplayingDecoder.callDecode(HintedReplayingDecoder.java:94) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:278) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10419) RocksDB purge should not utilise ArrayList to store multiple expired keys

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10419?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10419: ----------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > RocksDB purge should not utilise ArrayList to store multiple expired keys > ------------------------------------------------------------------------- > > Key: ISPN-10419 > URL: https://issues.jboss.org/browse/ISPN-10419 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 10.0.0.Beta4 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.CR1 > > > Currently the RocksDB purge method stores multiple keys that expire at the same time in a ArrayList associated with the expiry time. This is currently marshallable because ArrayList is serializable and we utilise Jboss-marshalling, however ISPN-10354 means this is no longer possible in embedded mode when `infinispan-jboss-marshalling` is not present. Therefore, we should create a `ExpiryBucket` that can be marshalled via the persistence marshaller i.e. protobuf based. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10432) Upgrade Protostream to 4.3.0.Alpha9

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10432?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10432: ----------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Upgrade Protostream to 4.3.0.Alpha9 > ----------------------------------- > > Key: ISPN-10432 > URL: https://issues.jboss.org/browse/ISPN-10432 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.Beta5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-94) Marshalling of immutable objects

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/IPROTO-94?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated IPROTO-94: ---------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Marshalling of immutable objects > -------------------------------- > > Key: IPROTO-94 > URL: https://issues.jboss.org/browse/IPROTO-94 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha8, 4.3.0.Final > > > These typically have final fields, may have getters for them but do not have setters. All fields should be read in advance and passed all at once to a constructor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10309) Convert Remaining Parts to Non Blocking & Reduce Thread Pools

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10309?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10309: ----------------------------------- Sprint: DataGrid Sprint #29, DataGrid Sprint #30, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #29, DataGrid Sprint #30, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Convert Remaining Parts to Non Blocking & Reduce Thread Pools > ------------------------------------------------------------- > > Key: ISPN-10309 > URL: https://issues.jboss.org/browse/ISPN-10309 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.1.0.Final > > > We would love to get our thread pools down to a single CPU thread pool (size = numCores) and a blocking thread pool (arbitrarily large). We may also require a scheduler pool for various options as well (limited size 1-2?). > To do this we need to remove remnants of our blocking code as possible. Possible issues for blocking are mostly around locks and io operations. > The persistence layer was completed with ISPN-9722 so that is not an issue. > The requirement around locking can be relaxed if the locks are guaranteed to be small in scope and do not wrap other blocking operations. An example would be a lock such as ones in CHM as long as we don't have large blocks for functional argument types. > If code cannot be made non blocking we must offload the operation to the blocking thread pool. Care must be taken to ensure that once the blocking portion of code is completed that we switch back the to CPU thread pool as soon as possible. The listener API for example is violating this and will run code in Infinispan from any thread that completes the listener that could be done from a user. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10385) Console Server Ng

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10385?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10385: ----------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Console Server Ng > ----------------- > > Key: ISPN-10385 > URL: https://issues.jboss.org/browse/ISPN-10385 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console-ng > > Create a new console using React and Patternfly 4 > - Create react app skeleton -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-119) Introduce a customizable TypeId mapper to support changing type ids for schema evolution

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/IPROTO-119?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated IPROTO-119: ----------------------------------- Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Introduce a customizable TypeId mapper to support changing type ids for schema evolution > ---------------------------------------------------------------------------------------- > > Key: IPROTO-119 > URL: https://issues.jboss.org/browse/IPROTO-119 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha13 > > > This should be a simple interface for mapping type ids in and out. Should be specified in Configuration -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-20) Should not be able to use the numbers 19000 though 19999 for fields

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/IPROTO-20?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated IPROTO-20: ---------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Should not be able to use the numbers 19000 though 19999 for fields > ------------------------------------------------------------------- > > Key: IPROTO-20 > URL: https://issues.jboss.org/browse/IPROTO-20 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9, 4.3.0.Final > > > See Assigning Tags in https://developers.google.com/protocol-buffers/docs/proto -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-13) Proto parser does not detect duplicate enum constant names

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/IPROTO-13?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated IPROTO-13: ---------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Proto parser does not detect duplicate enum constant names > ---------------------------------------------------------- > > Key: IPROTO-13 > URL: https://issues.jboss.org/browse/IPROTO-13 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.5.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.0.0.Alpha6, 4.0.0.Final > > > This should generate an error: > {code} > enum E { > A = 1; > A = 2; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-101) Enum values with same name in different classes clash

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/IPROTO-101?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated IPROTO-101: ----------------------------------- Sprint: DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36) > Enum values with same name in different classes clash > ----------------------------------------------------- > > Key: IPROTO-101 > URL: https://issues.jboss.org/browse/IPROTO-101 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.0.Alpha6 > Reporter: Ryan Emerson > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha10 > > > {code:java} > @ProtoName("TakeSiteOfflineResponse") > public enum TakeSiteOfflineResponse { > @ProtoEnumValue(number = 1) > NO_SUCH_SITE, > @ProtoEnumValue(number = 2) > ALREADY_OFFLINE, > @ProtoEnumValue(number = 3) > TAKEN_OFFLINE > } > @ProtoName("BringSiteOnlineResponse") > public enum BringSiteOnlineResponse { > @ProtoEnumValue(number = 1) > NO_SUCH_SITE, > @ProtoEnumValue(number = 2) > ALREADY_ONLINE, > @ProtoEnumValue(number = 3) > BROUGHT_ONLINE > } > {code} > Results in: > {code:java} > Enum value org.infinispan.test.TakeSiteOfflineResponse.NO_SUCH_SITE clashes with enum value org.infinispan.test.BringSiteOnlineResponse.NO_SUCH_SITE > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019