April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9092) Upgrade Protostream to 4.2.0.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9092?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9092: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade Protostream to 4.2.0.Final > ---------------------------------- > > Key: ISPN-9092 > URL: https://issues.jboss.org/browse/ISPN-9092 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.2.2.Final, 9.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9092) Upgrade Protostream to 4.2.0.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9092?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9092: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1 > Upgrade Protostream to 4.2.0.Final > ---------------------------------- > > Key: ISPN-9092 > URL: https://issues.jboss.org/browse/ISPN-9092 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.2.2.Final, 9.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9003) Clustered maxIdle expiration

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9003?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-9003: ------------------------------------- Upon further investigation iteration will have to do something different than a simple get. Otherwise it would cause possible concurrent remove expired operations (up to numOwners). There are 2 ways to fix this so far: 1. Use something like a segmented data container ISPN-5451 (prevents all the nodes from accessing the expired data) 2. We can change the iteration to not remove the entry but rather just report if it should be used or not. We could even in the case of when it expires set a last access time of a negative number which is a sign that it shouldn't query remote again (preventing it from going remote multiple times before entry is removed) For now #2 will be done and when segment data container is introduced we can move to that if desired. > Clustered maxIdle expiration > ---------------------------- > > Key: ISPN-9003 > URL: https://issues.jboss.org/browse/ISPN-9003 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 9.3.0.Beta1, 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9000) Send e-mails for nightly builds to Infinispan CI mailing list

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9000?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9000: ------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5897 > Send e-mails for nightly builds to Infinispan CI mailing list > ------------------------------------------------------------- > > Key: ISPN-9000 > URL: https://issues.jboss.org/browse/ISPN-9000 > Project: Infinispan > Issue Type: Bug > Components: CI > Reporter: Tristan Tarrant > Assignee: Vittorio Rigamonti > > The branch builds (master, stable, etc) should send results to the infinispan ci mailing list -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7420) Hot Rod enhancements for transcoding

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7420?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7420: ---------------------------------- Sprint: Sprint 9.3.0.Beta1 (was: Sprint 9.3.0.Alpha1) > Hot Rod enhancements for transcoding > ------------------------------------ > > Key: ISPN-7420 > URL: https://issues.jboss.org/browse/ISPN-7420 > Project: Infinispan > Issue Type: Feature Request > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > > Several enhancements will need to be made to the Hot Rod protocol to work with transcoding: > h3. Cache Writes (key + value) > * Cache write operations that include values should have an optional parameter to be able to define the MIME type of the key and value that is being written. When the optional parameter is sent to the server, it will enable the server to implicitly discover what the types of the key+value are. > * Once the first cache write has determined the key+value types, the clients do not need to send them again. If the client sends different types for the same cache, it should either result in the server ignoring it or an error (the former is preferable). > * To avoid sending unnecessary data, advanced clients could cache the key+value type for a given cache after the first write request and then don't send it again. > h3. Cache reads > * Any operation that involves retrieving data should optionally take the type that the value should be transcoded to when returning it back to the client. This enables data to be read in different formats. > * Within these operations, write operations that return previous values should be included. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9090) Create both thin and fat servers

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9090?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9090: ------------------------------- Component/s: Build Server > Create both thin and fat servers > -------------------------------- > > Key: ISPN-9090 > URL: https://issues.jboss.org/browse/ISPN-9090 > Project: Infinispan > Issue Type: Bug > Components: Build, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > The server build should create two servers: > * a thin one (to be pushed to maven and used for the testsuite) > * a fat one (to be used as the binary distro) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8936) Parameterized branding

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8936?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8936. -------------------------------- Fix Version/s: 9.3.0.Alpha1 (was: 9.3.0.Final) Resolution: Done > Parameterized branding > ---------------------- > > Key: ISPN-8936 > URL: https://issues.jboss.org/browse/ISPN-8936 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > The Infinispan name is included in a number of artifacts: > * javadocs > * documentation > * CLI > * Server startup banner > * Console > * zip distributions > These should be parameterizable for productization -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8998) Automatically release from CI

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8998?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8998: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5918 > Automatically release from CI > ----------------------------- > > Key: ISPN-8998 > URL: https://issues.jboss.org/browse/ISPN-8998 > Project: Infinispan > Issue Type: Bug > Components: Build, CI > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > The releases should happen via a Jenkins job: > * versioning, build and stage to nexus > * reversion and build of simple tutorials against stage repository to ensure that all artifacts are correctly published > * release and drop of nexus staging repo > * push tag and bump version to next snapshot on master branch -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8998) Automatically release from CI

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8998?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8998: ------------------------------- Fix Version/s: 9.3.0.Alpha1 > Automatically release from CI > ----------------------------- > > Key: ISPN-8998 > URL: https://issues.jboss.org/browse/ISPN-8998 > Project: Infinispan > Issue Type: Bug > Components: Build, CI > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > The releases should happen via a Jenkins job: > * versioning, build and stage to nexus > * reversion and build of simple tutorials against stage repository to ensure that all artifacts are correctly published > * release and drop of nexus staging repo > * push tag and bump version to next snapshot on master branch -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9090) Create both thin and fat servers

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9090?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9090: ------------------------------- Status: Open (was: New) > Create both thin and fat servers > -------------------------------- > > Key: ISPN-9090 > URL: https://issues.jboss.org/browse/ISPN-9090 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > The server build should create two servers: > * a thin one (to be pushed to maven and used for the testsuite) > * a fat one (to be used as the binary distro) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018