June 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10202) Rework SASL code to ease Elytron integration

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10202?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10202. --------------------------------- Resolution: Done > Rework SASL code to ease Elytron integration > -------------------------------------------- > > Key: ISPN-10202 > URL: https://issues.jboss.org/browse/ISPN-10202 > Project: Infinispan > Issue Type: Sub-task > Components: Security, Server > Affects Versions: 10.0.0.Beta3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4 > > > The way in which the current server interacts with SaslServerFactory is designed around WildFly's security realm. For ServerNG we need to refactor the code to east direct integration with Elytron. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10277) Spring XSD location should work with both http and https

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10277?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10277. --------------------------------- Resolution: Done > Spring XSD location should work with both http and https > -------------------------------------------------------- > > Key: ISPN-10277 > URL: https://issues.jboss.org/browse/ISPN-10277 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Affects Versions: 10.0.0.Beta3, 9.4.14.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.15.Final > > > The spring.schemas file should include both http and https variants of the schema -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10280) Deprecate org.infinispan.commons.marshall.Externalizer

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10280: ----------------------------------- Summary: Deprecate org.infinispan.commons.marshall.Externalizer Key: ISPN-10280 URL: https://issues.jboss.org/browse/ISPN-10280 Project: Infinispan Issue Type: Sub-task Components: Configuration, Core Affects Versions: 10.0.0.Beta3 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.Beta4 Once it's possible for a user to utilise a protostream based marshaller in embedded mode, we should deprecate Externalizers so they can removed in Infinispan 11. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9623) Create Protobuf based user marshaller

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9623?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9623: ------------------------------- Description: With the internal and persistence marshaller being protobuf based, we should also provide a user marshaller implementation that utilises protostream. Users should be able to configure annotated pojos or MessageMarshaller implementations for their objects, probably via a {{SerializationContextInitializer}} implementation. (was: With the internal and persistence marshaller being protobuf based, we should also provide a user marshaller implementation that utilises protostream. Users should be able to configure annotated pojos or MessageMarshaller implementations for their objects.) > Create Protobuf based user marshaller > ------------------------------------- > > Key: ISPN-9623 > URL: https://issues.jboss.org/browse/ISPN-9623 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > With the internal and persistence marshaller being protobuf based, we should also provide a user marshaller implementation that utilises protostream. Users should be able to configure annotated pojos or MessageMarshaller implementations for their objects, probably via a {{SerializationContextInitializer}} implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9715?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9715: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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)

5 years, 7 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 commented on ISPN-10246: ------------------------------------- Working Branch: https://github.com/ryanemerson/infinispan/tree/ISPN-10246 > 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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10276) Adapt StoreMigrator to support Infinispan 8-10 marshallers

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10276?page=com.atlassian.jira.plugin... ] Ryan Emerson commented on ISPN-10276: ------------------------------------- WIP branch here: https://github.com/ryanemerson/infinispan/tree/ISPN-10276 PR will be issued once ISPN-9621 has been merged. > Adapt StoreMigrator to support Infinispan 8-10 marshallers > ---------------------------------------------------------- > > Key: ISPN-10276 > URL: https://issues.jboss.org/browse/ISPN-10276 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > Currently the StoreMigrator only supports reading from Infinispan 8 stores. Due to the incompatibilities introduced with the Persistence marshaller changes, it's necessary for the migrator to now support reading from both 8/9 bytes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8756) Implement Single Port

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-8756?page=com.atlassian.jira.plugin.... ] Will Burns updated ISPN-8756: ----------------------------- Fix Version/s: 10.0.0.Beta4 > Implement Single Port > --------------------- > > Key: ISPN-8756 > URL: https://issues.jboss.org/browse/ISPN-8756 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Sebastian Laskawiec > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 10.0.0.Final > > > Design document: https://github.com/infinispan/infinispan-designs/blob/master/Single_port.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8756) Implement Single Port

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-8756?page=com.atlassian.jira.plugin.... ] Will Burns updated ISPN-8756: ----------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Implement Single Port > --------------------- > > Key: ISPN-8756 > URL: https://issues.jboss.org/browse/ISPN-8756 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Sebastian Laskawiec > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > > Design document: https://github.com/infinispan/infinispan-designs/blob/master/Single_port.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10279) Support Persistent Memory

by Jonathan Halliday (Jira)

Jonathan Halliday created ISPN-10279: ---------------------------------------- Summary: Support Persistent Memory Key: ISPN-10279 URL: https://issues.jboss.org/browse/ISPN-10279 Project: Infinispan Issue Type: Feature Request Reporter: Jonathan Halliday Persistent Memory (pmem) is memory, in that it fits in the DIMM slots and is accessed by load/store instructions via the L2 cache. But it's also persistent, in that it retains content without power. See e.g pmem.io for background. DAX aware filesystems on pmem are MUCH faster than fs on SSD. This makes them a good target for e.g. Soft-Index persistence of cache data. OpenJDK is being enhanced to support pmem, via http://openjdk.java.net/jeps/352 There is a library to provide a FileChannel-like abstraction over that pmem support, see https://github.com/jhalliday/turbinia This JIRA is a placeholder for the integration work to tweak sifs so that it can use pmem on systems where the hardware is available. Since it already uses FileChannel, that's a small incremental change. The necessary work is: Push a turbinia release to central so it can be consumed. Note that whilst actually using pmem will need a recent JDK, using the library's integration API won't, so Infinispan can still build/run on older JDKs. Change the sifs FileProvider so it tries to use pmem when possible. This is a minimal change set, requiring mainly the wiring to pass in maxFileSize config, which memory mapping will need but the current implementation doesn't use. Fix the tests, which don't currently work even without pmem. See ISPN-10189 Update docs as needed. Update the CI environment and test profiles so the pmem specific code gets exercised regularly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2019