January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5074) Update remote query quickstart with the new annotation driven Protostream marshalling

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5074?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5074: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.1.0.Final Resolution: Done Integrated in master. > Update remote query quickstart with the new annotation driven Protostream marshalling > ------------------------------------------------------------------------------------- > > Key: ISPN-5074 > URL: https://issues.jboss.org/browse/ISPN-5074 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: jdg > Fix For: 7.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

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

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3907?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3907: -------------------------------- Git Pull Request: https://github.com/infinispan/protostream/pull/21, https://github.com/infinispan/infinispan/pull/3242 (was: https://github.com/infinispan/protostream/pull/21) > Define a Protobuf annotation 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)

9 years, 3 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.... ] Adrian Nistor updated ISPN-5178: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.1.0.Final Resolution: Done Integrated in master. > 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 > Fix For: 7.1.0.Final > > > Currently only java.util.Collection is supported. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 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.... ] Adrian Nistor updated ISPN-5177: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. > 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)

9 years, 3 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.... ] Adrian Nistor commented on ISPN-5183: ------------------------------------- Integrated in master. > 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)

9 years, 3 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.... ] Adrian Nistor updated ISPN-5183: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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)

9 years, 3 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.... ] Adrian Nistor updated ISPN-5178: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/21 > 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)

9 years, 3 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.... ] Adrian Nistor updated ISPN-5177: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/21 > 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)

9 years, 3 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.... ] Adrian Nistor updated ISPN-5183: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/21 > 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)

9 years, 3 months

1
0
0 / 0

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

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3907?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3907: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/21 > Define a Protobuf annotation 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)

9 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2015