February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6252) Upgrade to Apache Lucene 5.5

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6252?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes edited comment on ISPN-6252 at 2/29/16 3:46 AM: ------------------------------------------------------------------ So there are two ways of taclking this I can think of: * The Infinispan module build consumes hibernate search module, but manipulate it to replace the internal Lucene version. This is a bit brittle. * Publish \[1\] and Hibernate Search depends on this module via an alias slot, like "lucene-slot". On Infinispan side, we consume hibernate search module but filter out the alias and use our own alias to a different lucene version, also coming from \[1\] Thoughts? \[1\] https://github.com/hibernate/lucene-modules was (Author: gustavonalle): So there are two ways of tacking this I can think of: * The Infinispan module build consumes hibernate search module, but manipulate it to replace the internal Lucene version. This is a bit brittle. * Publish \[1\] and Hibernate Search depends on this module via an alias slot, like "lucene-slot". On Infinispan side, we consume hibernate search module but filter out the alias and use our own alias to a different lucene version, also coming from \[1\] Thoughts? \[1\] https://github.com/hibernate/lucene-modules > Upgrade to Apache Lucene 5.5 > ---------------------------- > > Key: ISPN-6252 > URL: https://issues.jboss.org/browse/ISPN-6252 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 8.2.0.CR1 > > > Apache Lucene 5.5 is released now, and is "drop-in compatible" with versions 5.3 and 5.4 so you don't have to wait for an Hibernate Search release. > It's also being the last one for the 5.x series before 6, so I expect that we'll see some more micro releases for maintenance but essentially that this will be some form of long term commitment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6252) Upgrade to Apache Lucene 5.5

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6252?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes edited comment on ISPN-6252 at 2/29/16 3:46 AM: ------------------------------------------------------------------ So there are two ways of tackling this I can think of: * The Infinispan module build consumes hibernate search module, but manipulate it to replace the internal Lucene version. This is a bit brittle. * Publish \[1\] and Hibernate Search depends on this module via an alias slot, like "lucene-slot". On Infinispan side, we consume hibernate search module but filter out the alias and use our own alias to a different lucene version, also coming from \[1\] Thoughts? \[1\] https://github.com/hibernate/lucene-modules was (Author: gustavonalle): So there are two ways of taclking this I can think of: * The Infinispan module build consumes hibernate search module, but manipulate it to replace the internal Lucene version. This is a bit brittle. * Publish \[1\] and Hibernate Search depends on this module via an alias slot, like "lucene-slot". On Infinispan side, we consume hibernate search module but filter out the alias and use our own alias to a different lucene version, also coming from \[1\] Thoughts? \[1\] https://github.com/hibernate/lucene-modules > Upgrade to Apache Lucene 5.5 > ---------------------------- > > Key: ISPN-6252 > URL: https://issues.jboss.org/browse/ISPN-6252 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 8.2.0.CR1 > > > Apache Lucene 5.5 is released now, and is "drop-in compatible" with versions 5.3 and 5.4 so you don't have to wait for an Hibernate Search release. > It's also being the last one for the 5.x series before 6, so I expect that we'll see some more micro releases for maintenance but essentially that this will be some form of long term commitment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6252) Upgrade to Apache Lucene 5.5

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6252?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-6252: ----------------------------------------- So there are two ways of tacking this I can think of: * The Infinispan module build consumes hibernate search module, but manipulate it to replace the internal Lucene version. This is a bit brittle. * Publish \[1\] and Hibernate Search depends on this module via an alias slot, like "lucene-slot". On Infinispan side, we consume hibernate search module but filter out the alias and use our own alias to a different lucene version, also coming from \[1\] Thoughts? \[1\] https://github.com/hibernate/lucene-modules > Upgrade to Apache Lucene 5.5 > ---------------------------- > > Key: ISPN-6252 > URL: https://issues.jboss.org/browse/ISPN-6252 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 8.2.0.CR1 > > > Apache Lucene 5.5 is released now, and is "drop-in compatible" with versions 5.3 and 5.4 so you don't have to wait for an Hibernate Search release. > It's also being the last one for the 5.x series before 6, so I expect that we'll see some more micro releases for maintenance but essentially that this will be some form of long term commitment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6139) Delete a node from cluster

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6139?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-6139: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Delete a node from cluster > -------------------------- > > Key: ISPN-6139 > URL: https://issues.jboss.org/browse/ISPN-6139 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > > Nodes can be added but they can't be deleted from the console. Only stopped nodes should be able to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6142) Configuration view for cache container - Deployments

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6142?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-6142: ---------------------------------- Assignee: Pedro Zapata > Configuration view for cache container - Deployments > ---------------------------------------------------- > > Key: ISPN-6142 > URL: https://issues.jboss.org/browse/ISPN-6142 > Project: Infinispan > Issue Type: Task > Components: Console > Reporter: Pedro Zapata > Assignee: Pedro Zapata > > Implement deployments as described in: > https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6142) Configuration view for cache container - Deployments

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6142?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-6142: ---------------------------------- Assignee: Vladimir Blagojevic (was: Pedro Zapata) > Configuration view for cache container - Deployments > ---------------------------------------------------- > > Key: ISPN-6142 > URL: https://issues.jboss.org/browse/ISPN-6142 > Project: Infinispan > Issue Type: Task > Components: Console > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > > Implement deployments as described in: > https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6281) Document installation and configurations of Infinispan modules for Wildfly

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6281: --------------------------------------- Summary: Document installation and configurations of Infinispan modules for Wildfly Key: ISPN-6281 URL: https://issues.jboss.org/browse/ISPN-6281 Project: Infinispan Issue Type: Task Reporter: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6273) Add documentation for ClusterExecutor

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6273?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6273: -------------------------------- Status: Open (was: New) > Add documentation for ClusterExecutor > ------------------------------------- > > Key: ISPN-6273 > URL: https://issues.jboss.org/browse/ISPN-6273 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.2.0.Final > > > The ClusterExecutor was recently added allowing for execution of cluster wide events with the need of a cache. We need to document this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6273) Add documentation for ClusterExecutor

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6273?page=com.atlassian.jira.plugin.... ] Work on ISPN-6273 started by William Burns. ------------------------------------------- > Add documentation for ClusterExecutor > ------------------------------------- > > Key: ISPN-6273 > URL: https://issues.jboss.org/browse/ISPN-6273 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.2.0.Final > > > The ClusterExecutor was recently added allowing for execution of cluster wide events with the need of a cache. We need to document this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6038) ClientAsymmetricClusterTest.testAsymmetricCluster random failures

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6038?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-6038: --------------------------------------- This is quite tricky to resolve: the test is supposed to demonstrate that clients can connect to caches which are only defined on some nodes, but the way the PING is handled prevents this from succeeding if the first server to reply doesn't have the cache. If we really want to support asymmetric caches (and I think it's too much effort for the remote use-case anyway), PING should look at the hotrod topology cache for topology information instead of checking with its cache manager for cache existence. However, this raises another issue: the cache might have been defined after the server has started so the topology cache won't have any knowledge about it. This could be mitigated by adding a cacheStarted listener on the cacheManager which would update the topology information, but obviously this needs the cache to actually be started. All in all, I vote to suppress this test and declare asymmetric caches as unsupported in server. > ClientAsymmetricClusterTest.testAsymmetricCluster random failures > ----------------------------------------------------------------- > > Key: ISPN-6038 > URL: https://issues.jboss.org/browse/ISPN-6038 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, Test Suite - Server > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.2.0.CR1 > > > {{ClientAsymmetricClusterTest.testAsymmetricCluster}} is failing since the ISPN-5981 fix, which enabled {{pingOnStartup}} by default, and now returns {{null}} if the first server to be pinged doesn't have the cache defined. > {noformat} > 10:23:07,862 WARN (testng-ClientAsymmetricClusterTest:) [Codec21] ISPN004005: Error received from the server: org.infinispan.server.hotrod.CacheNotFoundException: Cache with name 'asymmetricCache' not found amongst the configured caches > 10:23:07,862 ERROR (testng-ClientAsymmetricClusterTest:) [UnitTestTestNGListener] Test testAsymmetricCluster(org.infinispan.client.hotrod.ClientAsymmetricClusterTest) failed. > java.lang.NullPointerException > at org.infinispan.client.hotrod.ClientAsymmetricClusterTest.testAsymmetricCluster(ClientAsymmetricClusterTest.java:38) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 February 2016