March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9004) Upgrade Hibernate Commons Annotations to 5.0.3.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9004?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9004: ---------------------------------- Fix Version/s: 9.2.2.Final (was: 9.2.1.Final) > Upgrade Hibernate Commons Annotations to 5.0.3.Final > ---------------------------------------------------- > > Key: ISPN-9004 > URL: https://issues.jboss.org/browse/ISPN-9004 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.2.2.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8993) LocalTopologyManager should not install a reset topology before conflict resolution

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8993?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8993: ---------------------------------- Fix Version/s: 9.2.2.Final (was: 9.2.1.Final) > LocalTopologyManager should not install a reset topology before conflict resolution > ----------------------------------------------------------------------------------- > > Key: ISPN-8993 > URL: https://issues.jboss.org/browse/ISPN-8993 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.2.Final > > > When the coordinator changes, either because the old one left or because there was a merge, the new coordinator first resets any ongoing rebalance, and then starts a rebalance with the new members. But some nodes could see the post-merge rebalance before the post-merge reset, and they need to reset any old data or inbound transfers first. > [LocalTopologyManagerImpl|https://github.com/infinispan/infinispan/blob/22...] is responsible for faking that reset topology update, in order to keep StateConsumerImpl simpler. The problem is that LocalTopologyManagerImpl also creates a reset topology update if the new coordinator started conflict resolution, and that topology update clears all the segments not owned by the local node in the preferred topology. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8972) Create Hibernate 5.3 module

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8972?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8972: ---------------------------------- Sprint: (was: Sprint 9.3.0.Beta1) > Create Hibernate 5.3 module > --------------------------- > > Key: ISPN-8972 > URL: https://issues.jboss.org/browse/ISPN-8972 > Project: Infinispan > Issue Type: Component Upgrade > Components: Hibernate Cache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.2.1.Final, 9.3.0.Alpha1 > > > Create Hibernate 5.3 module. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8972) Create Hibernate 5.3 module

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8972?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-8972. --------------------------------- Resolution: Done > Create Hibernate 5.3 module > --------------------------- > > Key: ISPN-8972 > URL: https://issues.jboss.org/browse/ISPN-8972 > Project: Infinispan > Issue Type: Component Upgrade > Components: Hibernate Cache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.2.1.Final, 9.3.0.Alpha1 > > > Create Hibernate 5.3 module. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8982) Hibernate ORM 5.3 2LC implementation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8982?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8982: ---------------------------------- Sprint: Sprint 9.3.0.Beta1 > Hibernate ORM 5.3 2LC implementation > ------------------------------------ > > Key: ISPN-8982 > URL: https://issues.jboss.org/browse/ISPN-8982 > Project: Infinispan > Issue Type: Task > Reporter: Radim Vansa > Assignee: Radim Vansa > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8972) Create Hibernate 5.3 module

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8972?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8972: ---------------------------------- Sprint: Sprint 9.3.0.Beta1 > Create Hibernate 5.3 module > --------------------------- > > Key: ISPN-8972 > URL: https://issues.jboss.org/browse/ISPN-8972 > Project: Infinispan > Issue Type: Component Upgrade > Components: Hibernate Cache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.2.1.Final, 9.3.0.Alpha1 > > > Create Hibernate 5.3 module. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1302) Check cache store implementations if they profit by the improvements in FileCacheStore

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1302?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1302. --------------------------------- Resolution: Out of Date > Check cache store implementations if they profit by the improvements in FileCacheStore > -------------------------------------------------------------------------------------- > > Key: ISPN-1302 > URL: https://issues.jboss.org/browse/ISPN-1302 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 5.0.0.CR8 > Reporter: Robert Stupp > Priority: Minor > > FileCacheStore has got a number of improvements > ISPN-1286 > ISPN-1288 > ISPN-1289 > ISPN-1290 > ISPN-1300 > ISPN-1301 > It should be checked, if other CacheStore implementation can benefit from these improvements. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1952) Use RESTEasy's HTTP frontend for the REST server

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1952?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1952. --------------------------------- Resolution: Out of Date > Use RESTEasy's HTTP frontend for the REST server > ------------------------------------------------ > > Key: ISPN-1952 > URL: https://issues.jboss.org/browse/ISPN-1952 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: NadirX > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Using RESTEasy's HTTP frontend would allow the following: > - allow starting of a containerless REST Server using the startServer.sh script in the distibution > - drop the need for JBossWeb in JDG > - Give us some noticeable performance improvements -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1833) Add EmbeddedCacheManager.getGlobalComponentRegistry

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1833?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1833. --------------------------------- Resolution: Done > Add EmbeddedCacheManager.getGlobalComponentRegistry > --------------------------------------------------- > > Key: ISPN-1833 > URL: https://issues.jboss.org/browse/ISPN-1833 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Minor > > You should be able to retrieve the global component registry out of the EmbeddedCacheManager. > Rather that having to do: > cache.getAdvancedCache().getComponentRegistry().getGlobalComponentRegistry() -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-984) Add ability to retrieve cache names remotely in Hot Rod

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-984?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant closed ISPN-984. -------------------------------- Resolution: Duplicate Issue > Add ability to retrieve cache names remotely in Hot Rod > ------------------------------------------------------- > > Key: ISPN-984 > URL: https://issues.jboss.org/browse/ISPN-984 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: hotrod > > A new operation would be needed to retrieve all cache names that are configured and running. > A new version of the protocol would need to be set up to deal with the new operation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018