November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9621) Split global marshaller into Persistence and Internal marshaller

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9621?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9621: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6240 > Split global marshaller into Persistence and Internal marshaller > ---------------------------------------------------------------- > > Key: ISPN-9621 > URL: https://issues.jboss.org/browse/ISPN-9621 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Loaders and Stores > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha1 > > > Currently the internal marshaller is used for marshalling key/value/metadata in store implementations. This means that it is possible for internal classes to be marshalled to a user store, which can cause compatibility issues if an internal classes serialization format changes (due to marshaller changes or addition/removal of fields). > We should separate the internal and persistence marshaller, only exposing the latter to stores via the InitializationContext. The persistence marshaller should only be able to serialize user key/values and the metadata/version data. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9621) Split global marshaller into Persistence and Internal marshaller

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9621?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9621: ------------------------------- Status: Open (was: New) > Split global marshaller into Persistence and Internal marshaller > ---------------------------------------------------------------- > > Key: ISPN-9621 > URL: https://issues.jboss.org/browse/ISPN-9621 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Loaders and Stores > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha1 > > > Currently the internal marshaller is used for marshalling key/value/metadata in store implementations. This means that it is possible for internal classes to be marshalled to a user store, which can cause compatibility issues if an internal classes serialization format changes (due to marshaller changes or addition/removal of fields). > We should separate the internal and persistence marshaller, only exposing the latter to stores via the InitializationContext. The persistence marshaller should only be able to serialize user key/values and the metadata/version data. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9620) Rolling Upgrade Marshaller Changes

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9620: ------------------------------- Sprint: Sprint 10.0.0.Alpha1 > Rolling Upgrade Marshaller Changes > ---------------------------------- > > Key: ISPN-9620 > URL: https://issues.jboss.org/browse/ISPN-9620 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Loaders and Stores > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha1 > > > In order to allow for compatibility between infinispan versions it is necessary for us to utilise a marshalling implementation at both the cluster (internal node-to-node communication) and persistence layer that is strictly defined but allows for future changes. This is necessary in order to facilitate both rolling and start/stop upgrades. Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9620) Rolling Upgrade Marshaller Changes

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9620: ------------------------------- Status: Open (was: New) > Rolling Upgrade Marshaller Changes > ---------------------------------- > > Key: ISPN-9620 > URL: https://issues.jboss.org/browse/ISPN-9620 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Loaders and Stores > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha1 > > > In order to allow for compatibility between infinispan versions it is necessary for us to utilise a marshalling implementation at both the cluster (internal node-to-node communication) and persistence layer that is strictly defined but allows for future changes. This is necessary in order to facilitate both rolling and start/stop upgrades. Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9620) Rolling Upgrade Marshaller Changes

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin.... ] Work on ISPN-9620 started by Ryan Emerson. ------------------------------------------ > Rolling Upgrade Marshaller Changes > ---------------------------------- > > Key: ISPN-9620 > URL: https://issues.jboss.org/browse/ISPN-9620 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Loaders and Stores > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha1 > > > In order to allow for compatibility between infinispan versions it is necessary for us to utilise a marshalling implementation at both the cluster (internal node-to-node communication) and persistence layer that is strictly defined but allows for future changes. This is necessary in order to facilitate both rolling and start/stop upgrades. Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7409) Replace external marshaller with user marshaller

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-7409?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7409: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/6240 > Replace external marshaller with user marshaller > ------------------------------------------------ > > Key: ISPN-7409 > URL: https://issues.jboss.org/browse/ISPN-7409 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Marshalling > Reporter: Galder Zamarreño > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > > ISPN-6906 brings much needed independence from JBoss Marshalling to our marshalling layer. One of the key aspects it brings it’s the separation between marshalling internal types we know about, e.g. String, byte[], CacheTopologyCommand...etc and external or unknown types, e.g. any types that extend Serializable. > Although this separation helps achieve objectives of ISPN-6906, it’s not an ideal solution: > * If user types map directly to primitive types supported by our internal marshaller, or types that depend on types that are marshalled by our internal marshaller, any changes made to the internal marshaller have a direct impact on the representation of the user types. > * In the ISPN-6906 implementation, Internal marshaller exposes its own externalizer table to the external marshaller so that it can lookup how to marshall internal types. This is done to support corner cases in Hibernate Search where some of the classes that Query module marshalls rely on the fact that some Hibernate Search classes are Serializable, but these classes reference Lucene query classes that are not for which there are externalizers defined. For query logic to work, externalizers have to be found while dealing with Serializable types are being traversed. Gustavo and Sane are aware of this issue and we should soon have externalizers for those Hibernate Search classes and avoid this issue altogether (see ISPN-7156). > So, rather than an external marshaller, a more suitable abstraction would be to have a user marshaller. The job of the user marshaller, which would be configurable, would be to marshall user types. The user marshaller should be independent of the internal marshaller, so it would not be able to piggyback on the internal externalizers. > Externalizers for user types could still be supported, by having a user externalizer table, purely used by the user marshaller. In fact, it would make sense that all externalizers that are configured in Infinispan (regardless of whether via xml, programmatic or via annotation) to be user externalizers. > User types are considered to be: > * Keys and values > * Metadata instances provided by the user via *withMetadata() calls > The benefits of the user marshaller are the following: > * Having the user marshaller configurable would make it easy to try out different marshallers when comparing how key/value types are marshalled, e.g. try out different ways to marshall Strings. > * An easier upgrade path for user types. Since user types no longer rely on internal marshaller details, Infinispan upgrades are easier to deal with. > For reference, custom commands that can be plugged via ModuleCommandFactory implementations would use the internal marshaller since these commands often marshall internal types, e.g. Address. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9692) Add ability to override maxClauseCount

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-9692: -------------------------------------- Summary: Add ability to override maxClauseCount Key: ISPN-9692 URL: https://issues.jboss.org/browse/ISPN-9692 Project: Infinispan Issue Type: Enhancement Components: Remote Querying, Server Reporter: Wolf-Dieter Fink Assignee: Adrian Nistor We are using the Hotrod client, and need the ability to specify or override the maxClauseCount setting, otherwise, we get the following error message: - org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 setting This will occur when there are more than 1024 "IN" conditions specified on the query builder. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9688) Internal REST server modularization

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-9688?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9688: ------------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/6380 > Internal REST server modularization > ----------------------------------- > > Key: ISPN-9688 > URL: https://issues.jboss.org/browse/ISPN-9688 > Project: Infinispan > Issue Type: Enhancement > Components: REST > Affects Versions: 9.4.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Alpha1 > > > To support the many new resources and multiple API concurrent versions as described in https://issues.jboss.org/browse/ISPN-8535, the REST server should evolve so that it requires minimal changes to add new resources and map them to paths/action. This will also allow better work parallelization to create the v2 API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9617) Create remote multimap simple example

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9617?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-9617. -------------------------------- Fix Version/s: 9.4.1.Final Resolution: Done > Create remote multimap simple example > ------------------------------------- > > Key: ISPN-9617 > URL: https://issues.jboss.org/browse/ISPN-9617 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 9.4.0.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 9.4.1.Final > > > Showcase remote multimap simple tutorial -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9407) FunctionalMapImpl.create does not inherit cache settings for Expiration and Eviction

by Ben Gardner (Jira)

[ https://issues.jboss.org/browse/ISPN-9407?page=com.atlassian.jira.plugin.... ] Ben Gardner updated ISPN-9407: ------------------------------ Priority: Blocker (was: Major) > FunctionalMapImpl.create does not inherit cache settings for Expiration and Eviction > ------------------------------------------------------------------------------------ > > Key: ISPN-9407 > URL: https://issues.jboss.org/browse/ISPN-9407 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.7.Final, 9.3.1.Final > Reporter: Ben Gardner > Priority: Blocker > > http://infinispan.org/docs/stable/user_guide/user_guide.html#functional_m... > FunctionalMapImpl.create() does not inherit cache settings for Expiration and Eviction. > Because of this, when adding the entries via the readwritemap, entries never expire. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 November 2018