May 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10037) Create documentation source for Infinispan Operator

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10037?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10037: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create documentation source for Infinispan Operator > --------------------------------------------------- > > Key: ISPN-10037 > URL: https://issues.jboss.org/browse/ISPN-10037 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Define and develop a set of titles based on customer use cases for the Infinispan operator. Docs should be sourced as modular asciidoc under infinispan-operator/documentation/asciidoc -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10246) Add build step to check protobuf schema changes are backwards compatible

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10246?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10246: -------------------------------- Status: Open (was: New) > Add build step to check protobuf schema changes are backwards compatible > ------------------------------------------------------------------------ > > Key: ISPN-10246 > URL: https://issues.jboss.org/browse/ISPN-10246 > Project: Infinispan > Issue Type: Sub-task > Components: Build > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > We should fail builds if they introduce backwards incompatible changes to our generated .proto files in order to ensure that future ISPN versions can always read data serialized from this version onwards. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10246) Add build step to check protobuf schema changes are backwards compatible

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10246?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10246: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6906 > Add build step to check protobuf schema changes are backwards compatible > ------------------------------------------------------------------------ > > Key: ISPN-10246 > URL: https://issues.jboss.org/browse/ISPN-10246 > Project: Infinispan > Issue Type: Sub-task > Components: Build > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > We should fail builds if they introduce backwards incompatible changes to our generated .proto files in order to ensure that future ISPN versions can always read data serialized from this version onwards. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10246) A build step to check protobuf schema changes are backwards compatible

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10246: ----------------------------------- Summary: A build step to check protobuf schema changes are backwards compatible Key: ISPN-10246 URL: https://issues.jboss.org/browse/ISPN-10246 Project: Infinispan Issue Type: Sub-task Components: Build Affects Versions: 10.0.0.Beta3 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.Beta4 We should fail builds if they introduce backwards incompatible changes to our generated .proto files in order to ensure that future ISPN versions can always read data serialized from this version onwards. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10246) Add build step to check protobuf schema changes are backwards compatible

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10246?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10246: -------------------------------- Summary: Add build step to check protobuf schema changes are backwards compatible (was: A build step to check protobuf schema changes are backwards compatible) > Add build step to check protobuf schema changes are backwards compatible > ------------------------------------------------------------------------ > > Key: ISPN-10246 > URL: https://issues.jboss.org/browse/ISPN-10246 > Project: Infinispan > Issue Type: Sub-task > Components: Build > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > We should fail builds if they introduce backwards incompatible changes to our generated .proto files in order to ensure that future ISPN versions can always read data serialized from this version onwards. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9716) Update internal remote listener code to support non blocking

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9716?page=com.atlassian.jira.plugin.... ] Will Burns updated ISPN-9716: ----------------------------- Status: Open (was: New) > Update internal remote listener code to support non blocking > ------------------------------------------------------------ > > Key: ISPN-9716 > URL: https://issues.jboss.org/browse/ISPN-9716 > Project: Infinispan > Issue Type: Sub-task > Components: Listeners > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > > With ISPN-9714 we will not be able to have non blocking listeners. We need to update all of our remote listeners to use non blocking properly. > Note that the client listeners themselves currently do not send a response, so this does not mean to update our client listener objects, but rather the code supporting them (ie. ClientListenerRegistry). -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9716) Update internal remote listener code to support non blocking

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9716?page=com.atlassian.jira.plugin.... ] Work on ISPN-9716 started by Will Burns. ---------------------------------------- > Update internal remote listener code to support non blocking > ------------------------------------------------------------ > > Key: ISPN-9716 > URL: https://issues.jboss.org/browse/ISPN-9716 > Project: Infinispan > Issue Type: Sub-task > Components: Listeners > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > > With ISPN-9714 we will not be able to have non blocking listeners. We need to update all of our remote listeners to use non blocking properly. > Note that the client listeners themselves currently do not send a response, so this does not mean to update our client listener objects, but rather the code supporting them (ie. ClientListenerRegistry). -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9715) Update internal embedded listeners to be non blocking

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9715?page=com.atlassian.jira.plugin.... ] Will Burns updated ISPN-9715: ----------------------------- Fix Version/s: 10.0.0.Beta4 > Update internal embedded listeners to be non blocking > ----------------------------------------------------- > > Key: ISPN-9715 > URL: https://issues.jboss.org/browse/ISPN-9715 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Listeners > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4 > > > With ISPN-9714 it will be possible to have a listener perform non blocking operations. Also any listener that doesn't return a CompletionStage is invoked in a different thread. We should convert all of our internal listeners to return a CompletionStage if they can, so that we don't have to incur the cost of switching threads to execute them. > We need to ensure that all embedded listeners return a CompletionStage and never block the current thread. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9722) Perform all CacheStore operations on a separate thread

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9722?page=com.atlassian.jira.plugin.... ] Will Burns updated ISPN-9722: ----------------------------- Fix Version/s: 10.0.0.Beta4 > Perform all CacheStore operations on a separate thread > ------------------------------------------------------ > > Key: ISPN-9722 > URL: https://issues.jboss.org/browse/ISPN-9722 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4, 10.0.0.Final > > > Persistence is one of the few remaining systems that are not non blocking. This needs to be remedied. We will eventually need to add an SPI that does this, but for now we need to offload the persistence operations to a different thread pool. > This should only require changes in the PersistenceManager to return non blocking methods (ie. return CompletionStage). We should then update references to use non blocking when possible. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10245) Spring Session bug when session id changes

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-10245?page=com.atlassian.jira.plugin... ] Katia Aresti updated ISPN-10245: -------------------------------- Summary: Spring Session bug when session id changes (was: Spring Session bug) > Spring Session bug when session id changes > ------------------------------------------ > > Key: ISPN-10245 > URL: https://issues.jboss.org/browse/ISPN-10245 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Katia Aresti > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

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 May 2019