January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3907) Define a Protobuf custom option for defining numeric IDs for types

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3907?page=com.atlassian.jira.plugin.... ] Work on ISPN-3907 started by Adrian Nistor. ------------------------------------------- > Define a Protobuf custom option for defining numeric IDs for types > ------------------------------------------------------------------ > > Key: ISPN-3907 > URL: https://issues.jboss.org/browse/ISPN-3907 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.1.0.Final > > > Currently the wire format of all Protobuf encoded keys and values contains a header/envelope that has some metadata information, like the fully qualified type name (that is protobuf type name, not java) of the object encoded in the message. This information is needed so that the other end can decode the message. And we added it because the Protobuf spec assumes both ends are aware of the message type, which is not the case most of the time. > While this approach solves the problem nicely, it becomes very inefficient is the FQN is long, which is usually the case, as people tend to stick the domain name of their company + package app name into it. > Solution: provide alternative unique numeric IDs to all types. The IDs can be added to message type definitions in the protobuf schema and the user is in charge of guaranteeing their uniqueness while the system must check and enforce the uniqueness when a schema is registered ib the ProtobufMetadataManager. To do this we define a custom Protobuf Message type option that accepts a numeric value. If such a numeric ID was assigned to the type then when it is serialized in protobuf the system has to use this id in the header rather that the FQN string. > This option should not be mandatory. Existing apps should work without requiring source code changes or recompiling providing that the relevant jars are upgraded in both client and server to support the new header encoding. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5183) Add java.util.Date support to Protostream's MessageMarshaller.ProtoStreamWriter/Reader

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5183?page=com.atlassian.jira.plugin.... ] Work on ISPN-5183 started by Adrian Nistor. ------------------------------------------- > Add java.util.Date support to Protostream's MessageMarshaller.ProtoStreamWriter/Reader > -------------------------------------------------------------------------------------- > > Key: ISPN-5183 > URL: https://issues.jboss.org/browse/ISPN-5183 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Affects Versions: 7.1.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.1.0.Final > > > Protobuf does not have a native Date type. The common practice is to use a 64 bit value to encode a timestamp in milliseconds. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5177) Protostream should throw a meaningful error message if the marshalled class does not have a suitable constructor

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5177?page=com.atlassian.jira.plugin.... ] Work on ISPN-5177 started by Adrian Nistor. ------------------------------------------- > Protostream should throw a meaningful error message if the marshalled class does not have a suitable constructor > ---------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5177 > URL: https://issues.jboss.org/browse/ISPN-5177 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.1.0.CR2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.1.0.Final > > > A non-private no argument constructor is requried. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5178) Protostream should support arrays for repeated fields

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5178?page=com.atlassian.jira.plugin.... ] Work on ISPN-5178 started by Adrian Nistor. ------------------------------------------- > Protostream should support arrays for repeated fields > ----------------------------------------------------- > > Key: ISPN-5178 > URL: https://issues.jboss.org/browse/ISPN-5178 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Affects Versions: 7.1.0.CR2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > Currently only java.util.Collection is supported. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5190) DefaultExecutorService throws ISE if constructed with ManagedExecutorService

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-5190?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated ISPN-5190: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3239 > DefaultExecutorService throws ISE if constructed with ManagedExecutorService > ---------------------------------------------------------------------------- > > Key: ISPN-5190 > URL: https://issues.jboss.org/browse/ISPN-5190 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 7.0.3.Final, 7.1.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > ManagedExecutorService.isShutdown() always throws an IllegalStateException per section 3.1.6.1 "Java EE Product Provider Requirements" the JEE concurrency specification. > However, the DefaultCacheManager constructor always calls the isShutdown() method of the delegate ExecutorService. This prevents DefaultExecutorService from being constructed with a ManagedExecutorService. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5190) DefaultExecutorService throws ISE if constructed with ManagedExecutorService

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-5190?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated ISPN-5190: ------------------------------- Description: ManagedExecutorService.isShutdown() always throws an IllegalStateException per section 3.1.6.1 "Java EE Product Provider Requirements" of the JEE concurrency specification. However, the DefaultCacheManager constructor always calls the isShutdown() method of the delegate ExecutorService. This prevents DefaultExecutorService from being constructed with a ManagedExecutorService. was: ManagedExecutorService.isShutdown() always throws an IllegalStateException per section 3.1.6.1 "Java EE Product Provider Requirements" the JEE concurrency specification. However, the DefaultCacheManager constructor always calls the isShutdown() method of the delegate ExecutorService. This prevents DefaultExecutorService from being constructed with a ManagedExecutorService. > DefaultExecutorService throws ISE if constructed with ManagedExecutorService > ---------------------------------------------------------------------------- > > Key: ISPN-5190 > URL: https://issues.jboss.org/browse/ISPN-5190 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 7.0.3.Final, 7.1.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > ManagedExecutorService.isShutdown() always throws an IllegalStateException per section 3.1.6.1 "Java EE Product Provider Requirements" of the JEE concurrency specification. > However, the DefaultCacheManager constructor always calls the isShutdown() method of the delegate ExecutorService. This prevents DefaultExecutorService from being constructed with a ManagedExecutorService. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5190) DefaultExecutorService throws ISE if constructed with ManagedExecutorService

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-5190?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned ISPN-5190: ---------------------------------- Assignee: Paul Ferraro > DefaultExecutorService throws ISE if constructed with ManagedExecutorService > ---------------------------------------------------------------------------- > > Key: ISPN-5190 > URL: https://issues.jboss.org/browse/ISPN-5190 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 7.0.3.Final, 7.1.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > ManagedExecutorService.isShutdown() always throws an IllegalStateException per section 3.1.6.1 "Java EE Product Provider Requirements" the JEE concurrency specification. > However, the DefaultCacheManager constructor always calls the isShutdown() method of the delegate ExecutorService. This prevents DefaultExecutorService from being constructed with a ManagedExecutorService. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5190) DefaultExecutorService throws ISE if constructed with ManagedExecutorService

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-5190: ---------------------------------- Summary: DefaultExecutorService throws ISE if constructed with ManagedExecutorService Key: ISPN-5190 URL: https://issues.jboss.org/browse/ISPN-5190 Project: Infinispan Issue Type: Bug Components: Distributed Execution and Map/Reduce Affects Versions: 7.1.0.CR2, 7.0.3.Final Reporter: Paul Ferraro ManagedExecutorService.isShutdown() always throws an IllegalStateException per section 3.1.6.1 "Java EE Product Provider Requirements" the JEE concurrency specification. However, the DefaultCacheManager constructor always calls the isShutdown() method of the delegate ExecutorService. This prevents DefaultExecutorService from being constructed with a ManagedExecutorService. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5189) Add a default compute function to the Cache interface

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5189: ------------------------------------- Summary: Add a default compute function to the Cache interface Key: ISPN-5189 URL: https://issues.jboss.org/browse/ISPN-5189 Project: Infinispan Issue Type: Feature Request Components: Core Reporter: Tristan Tarrant Java 8 has extended the Map interface with computeIfAbsent and putIfAbsent methods to support memoization. We could take this one step further by allowing setting a default mapping function using the Function<? super K,? extends V> signature so that invoking a get operation on a non-existent or expired entry will compute it and store it in the cache. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5188) Indexing of JSON values

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5188: ------------------------------------- Summary: Indexing of JSON values Key: ISPN-5188 URL: https://issues.jboss.org/browse/ISPN-5188 Project: Infinispan Issue Type: Feature Request Components: Remote Protocols, Remote Querying Reporter: Tristan Tarrant Introduce a JSON marshaller so that JSON values can be indexed and queried using the ProtoBuf schemas. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2015