May 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7878) Distribution build fails due to errors in documentation groovy script

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7878?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7878: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Distribution build fails due to errors in documentation groovy script > --------------------------------------------------------------------- > > Key: ISPN-7878 > URL: https://issues.jboss.org/browse/ISPN-7878 > Project: Infinispan > Issue Type: Bug > Components: Build process > Reporter: Ryan Emerson > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 9.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3128) Better support for (Spring) read caching

by Adrian Moos (JIRA)

[ https://issues.jboss.org/browse/ISPN-3128?page=com.atlassian.jira.plugin.... ] Adrian Moos commented on ISPN-3128: ----------------------------------- Correct, so changing Cache.get(Object, Callable) to use putForExternalRead() would only be a partial solution - but still better than nothing. > Better support for (Spring) read caching > ---------------------------------------- > > Key: ISPN-3128 > URL: https://issues.jboss.org/browse/ISPN-3128 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Affects Versions: 5.3.0.Beta2 > Environment: Spring 3.1+ > Reporter: Mike Noordermeer > Assignee: Gustavo Fernandes > > We're having a bit of an issue using Infinispan as backing cache for Spring's Caching annotations. The reasons are clear, but I haven't found a proper solution yet. I thought I would describe the issues in a feature request, so we can try to make the necessary changes to fix the situation. > As already described in [the forums|https://community.jboss.org/thread/201086], an Infinispan cache in invalidation mode sends an invalidation message to other cache nodes if something is put into the cache. This conflicts with Spring's idea of {{@Cacheable}} annotations, which are ment to provide read caching for methods. Imagine the following scenario: > - Method A is annotated with {{@Cacheable}}, backed by a cache in invalidation mode > - Node X calls Method A, the method is executed and the return value is locally cached (and an invalidation message is sent to Node Y) > - Node Y calls Method A, the method is executed and the return value is locally cached, *also, the cache of Node X is invalidated* > - Node X calls Method A and has to execute the method again, since its cache is gone, etc... etc... > The reason we want to be able to invalidate the read cache, is because if the application executed an update method for the underlying data (usually marked with {{@CacheEvict}} or {{@CachePut}}) we *do* want to invalidate the other ndoes. > In Infinispan, this problem can be solved by caching using {{cache.putForExternalRead()}}. That will not invalidate other caches on a put, but will invalidate the cache when asked explicitly. However, simply changing {{put()}} to {{putForExternalRead()}} in {{SpringCache}} leads to a couple of other issues: > - This is probably not the behaviour everyone wants (people that do not use Spring annotations, but expect the usual Infinispan behaviour). > - Changing {{put()}} to {{putForExternalRead()}} would break the expected {{@CachePut}} behaviour (a new value is generated, so the old values should be invalidated), but it would fix {{@Cacheable}} behaviour. > Maybe there should be an option in the factory bean to switch between {{put()}} and {{putForExternalRead()}}? Maybe Spring should change or amend its interface so we can differentiate between calls coming from {{@CachePut}} and calls coming from {{@Cacheable}}? An other option is to make the invalidation behaviour configurable in Infinispan (that's the way Ehcache handles this issue, you can choose if puts or updates should be replicated, or just replicate invalidations). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7580) Use of marsheller is not consistent in all places

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/ISPN-7580?page=com.atlassian.jira.plugin.... ] Ramesh Reddy resolved ISPN-7580. -------------------------------- Resolution: Out of Date This functionality supported now with a different JIRA > Use of marsheller is not consistent in all places > ------------------------------------------------- > > Key: ISPN-7580 > URL: https://issues.jboss.org/browse/ISPN-7580 > Project: Infinispan > Issue Type: Bug > Components: Marshalling, Remote Querying > Reporter: Ramesh Reddy > Assignee: Adrian Nistor > > Usage of extended ProtoStreamMarshaller is not consistent across all the code paths. For the purposes of Teiid translator, I have extended ProtoStreamMarshaller which knows to read/write byte streams in portable fashion for given message type, which are representions of a relational table in Teiid. This works fine, if I just use cache's get/put calls. > However, the same fails when used with RemoteQuery or Continuous query. The reason is, these classes circumvent extended Marsheller and go directly to serialization context registered to do the wrapping/unwrapping. Not only that there are few places code will type cast the SerializationContext to SerializationContextImpl object. Thus I can not even provide my own Serializer nor I can extend this as SerializationContextImpl is declared as final. These need to be corrected such that extended marsheller is used rather than hard coding them. > I am guessing this is first time anyone has even done this without using dedicated java classes as marshellers. > This is extremely critical for me to be fixed to move forward, I can provide the pull request for it? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7873) Improve Infinispan use on Spring out-of-the-box

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7873?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7873: ----------------------------------- Description: An umbrella JIRA to make sure Infinispan appears as option whenever there's an opportunity to integrate within a Spring application. Individual subtasks will be created for each of the integration points. Within Spring Boot, seems like Infinispan is used in multiple places: https://github.com/spring-projects/spring-boot/search?l=Maven+POM&q=infin... Analise those uses and see which gaps are present, which should be covered by the subtasks. was:An umbrella JIRA to make sure Infinispan appears as option whenever there's an opportunity to integrate within a Spring application. Individual subtasks will be created for each of the integration points. > Improve Infinispan use on Spring out-of-the-box > ----------------------------------------------- > > Key: ISPN-7873 > URL: https://issues.jboss.org/browse/ISPN-7873 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > An umbrella JIRA to make sure Infinispan appears as option whenever there's an opportunity to integrate within a Spring application. Individual subtasks will be created for each of the integration points. > Within Spring Boot, seems like Infinispan is used in multiple places: > https://github.com/spring-projects/spring-boot/search?l=Maven+POM&q=infin... > Analise those uses and see which gaps are present, which should be covered by the subtasks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7877) Infinispan in Spring Boot

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7877?page=com.atlassian.jira.plugin.... ] Galder Zamarreño deleted ISPN-7877: ----------------------------------- > Infinispan in Spring Boot > ------------------------- > > Key: ISPN-7877 > URL: https://issues.jboss.org/browse/ISPN-7877 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > It seems like it's already used, so make sure the correct dependencies are used, and the usage is correct: > https://github.com/spring-projects/spring-boot/blob/a4bcd20b642fd2dc6847f... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7877) Infinispan in Spring Boot

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7877?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7877: ----------------------------------- Summary: Infinispan in Spring Boot (was: Infinispan in Spring Boot Cache Sample) > Infinispan in Spring Boot > ------------------------- > > Key: ISPN-7877 > URL: https://issues.jboss.org/browse/ISPN-7877 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > It seems like it's already used, so make sure the correct dependencies are used, and the usage is correct: > https://github.com/spring-projects/spring-boot/blob/a4bcd20b642fd2dc6847f... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7878) Distribution build fails due to errors in documentation groovy script

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7878?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7878: ------------------------------- Summary: Distribution build fails due to errors in documentation groovy script (was: Distribution build fails due to errors in groovy script) > Distribution build fails due to errors in documentation groovy script > --------------------------------------------------------------------- > > Key: ISPN-7878 > URL: https://issues.jboss.org/browse/ISPN-7878 > Project: Infinispan > Issue Type: Bug > Components: Build process > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Blocker > Fix For: 9.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7877) Infinispan in Spring Boot Cache Sample

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-7877: -------------------------------------- Summary: Infinispan in Spring Boot Cache Sample Key: ISPN-7877 URL: https://issues.jboss.org/browse/ISPN-7877 Project: Infinispan Issue Type: Sub-task Reporter: Galder Zamarreño Assignee: Galder Zamarreño It seems like it's already used, so make sure the correct dependencies are used, and the usage is correct: https://github.com/spring-projects/spring-boot/blob/a4bcd20b642fd2dc6847f... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7878) Distribution build fails due to errors in groovy script

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-7878: ---------------------------------- Summary: Distribution build fails due to errors in groovy script Key: ISPN-7878 URL: https://issues.jboss.org/browse/ISPN-7878 Project: Infinispan Issue Type: Bug Components: Build process Reporter: Ryan Emerson Assignee: Ryan Emerson Priority: Blocker Fix For: 9.1.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7875) Infinispan as Spring Data backend

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-7875: -------------------------------------- Summary: Infinispan as Spring Data backend Key: ISPN-7875 URL: https://issues.jboss.org/browse/ISPN-7875 Project: Infinispan Issue Type: Sub-task Reporter: Galder Zamarreño Assignee: Galder Zamarreño -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 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 2017