January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2575) KeyTransformer registration is required on all nodes of the cluster, in case of custom keys

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2575: -------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > KeyTransformer registration is required on all nodes of the cluster, in case of custom keys > ------------------------------------------------------------------------------------------- > > Key: ISPN-2575 > URL: https://issues.jboss.org/browse/ISPN-2575 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Affects Versions: 5.2.0.Beta5 > Reporter: Anna Manukyan > Assignee: Adrian Nistor > Attachments: ClusteredCacheTest.java > > > The case is the following: > I have a clustered cache on which I want to perform a search. I'm doing the following: > I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception: > java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer > When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager. > The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

1 week, 4 days

2
1
0 / 0

[JBoss JIRA] (ISPN-7423) Restructure Hot Rod and Java client documentation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7423?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7423: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR1 Resolution: Done > Restructure Hot Rod and Java client documentation > ------------------------------------------------- > > Key: ISPN-7423 > URL: https://issues.jboss.org/browse/ISPN-7423 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core, Documentation-Servers, Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.CR1, 9.0.0.Final > > > Restructure so that all sections can easily be accessed via the table of contents. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7426) Upgrade to Hibernate Search 5.7.0.CR1 and Hibernate ORM 5.2.7.Final

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-7426?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-7426: ---------------------------------- Status: Open (was: New) > Upgrade to Hibernate Search 5.7.0.CR1 and Hibernate ORM 5.2.7.Final > ------------------------------------------------------------------- > > Key: ISPN-7426 > URL: https://issues.jboss.org/browse/ISPN-7426 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process, Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.0.CR1, 9.0.0.Final > > > The main goal of this issue is to upgrade to the Hibernate Search 5.7.x family. > Hibernate ORM needs to be aligned as we use the combination in some tests; they don't strictly need to be aligned for our functional purposes but it makes the upgrade much simpler. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7426) Upgrade to Hibernate Search 5.7.0.CR1 and Hibernate ORM 5.2.7.Final

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-7426?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-7426: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4817 > Upgrade to Hibernate Search 5.7.0.CR1 and Hibernate ORM 5.2.7.Final > ------------------------------------------------------------------- > > Key: ISPN-7426 > URL: https://issues.jboss.org/browse/ISPN-7426 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process, Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.0.CR1, 9.0.0.Final > > > The main goal of this issue is to upgrade to the Hibernate Search 5.7.x family. > Hibernate ORM needs to be aligned as we use the combination in some tests; they don't strictly need to be aligned for our functional purposes but it makes the upgrade much simpler. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6386) Remove max-entries from the documentation

by sw0x2A sw0x2A (JIRA)

[ https://issues.jboss.org/browse/ISPN-6386?page=com.atlassian.jira.plugin.... ] sw0x2A sw0x2A commented on ISPN-6386: ------------------------------------- This also applies for ISPN 8.2.1. max-entries is mentioned in [docs|http://infinispan.org/docs/8.2.x/user_guide/user_guide.html] but ISPN throws exception when max-entries is used in config: {code} 16:09:28,709 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final] at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildfly-server-2.0.10.Final.jar:2.0.10.Final] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_111] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[144,21] Message: WFLYCTL0197: Unexpected attribute 'max-entries' encountered at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final] at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseEviction(InfinispanSubsystemXMLReader.java:1108) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseCacheElement(InfinispanSubsystemXMLReader.java:932) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseDistributedCache(InfinispanSubsystemXMLReader.java:804) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseContainer(InfinispanSubsystemXMLReader.java:281) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.readElement(InfinispanSubsystemXMLReader.java:95) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.readElement(InfinispanSubsystemXMLReader.java:68) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.2.0.Final.jar:1.2.0.Final] at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final] at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:546) [wildfly-server-2.0.10.Final.jar:2.0.10.Final] at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:242) [wildfly-server-2.0.10.Final.jar:2.0.10.Final] at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141) [wildfly-server-2.0.10.Final.jar:2.0.10.Final] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [wildfly-server-2.0.10.Final.jar:2.0.10.Final] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49) [wildfly-server-2.0.10.Final.jar:2.0.10.Final] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.2.0.Final.jar:1.2.0.Final] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final] ... 3 more {code} Works if I replace max-entries attribute with size. > Remove max-entries from the documentation > ----------------------------------------- > > Key: ISPN-6386 > URL: https://issues.jboss.org/browse/ISPN-6386 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Sebastian Łaskawiec > Assignee: Adrian Nistor > Fix For: 9.0.0.CR1 > > > In ISPN 9 we use size instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7419) Enable system property replacement in Hot Rod configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7419?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7419: ---------------------------------- Status: Open (was: New) > Enable system property replacement in Hot Rod configuration > ------------------------------------------------------------ > > Key: ISPN-7419 > URL: https://issues.jboss.org/browse/ISPN-7419 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.CR1 > > > The Hot Rod configuration does not expand system properties. This should be enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7419) Enable system property replacement in Hot Rod configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7419?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7419: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4816 > Enable system property replacement in Hot Rod configuration > ------------------------------------------------------------ > > Key: ISPN-7419 > URL: https://issues.jboss.org/browse/ISPN-7419 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.CR1 > > > The Hot Rod configuration does not expand system properties. This should be enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7426) Upgrade to Hibernate Search 5.7.0.CR1 and Hibernate ORM 5.2.7.Final

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-7426: ------------------------------------- Summary: Upgrade to Hibernate Search 5.7.0.CR1 and Hibernate ORM 5.2.7.Final Key: ISPN-7426 URL: https://issues.jboss.org/browse/ISPN-7426 Project: Infinispan Issue Type: Component Upgrade Components: Build process, Embedded Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 9.0.0.CR1, 9.0.0.Final The main goal of this issue is to upgrade to the Hibernate Search 5.7.x family. Hibernate ORM needs to be aligned as we use the combination in some tests; they don't strictly need to be aligned for our functional purposes but it makes the upgrade much simpler. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7425) Enable admins to delete configuration subsections

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7425?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7425: -------------------------------------- Motivation: we need to resolve JDG-695 but in a consistent approach > Enable admins to delete configuration subsections > ------------------------------------------------- > > Key: ISPN-7425 > URL: https://issues.jboss.org/browse/ISPN-7425 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Beta2 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.CR1 > > > We need to add the ability to remove configuration subsections (locking, expiration etc) and make it consistent across configuration screens. > UI perspective: We could have a delete icon (red cross or trash can etc) in the "panel-title" div of the section that a user is editing. If the user chooses to delete this sections config, then they should be presented with a message screen saying "<section> has not been defined, would you like to define this now?" similar to how we ask users to define container security when they click on the security section. Similarly, if a user loads an existing config with a section undefined, the aforementioned message should be displayed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7425) Enable admins to delete configuration subsections

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-7425: ----------------------------------------- Summary: Enable admins to delete configuration subsections Key: ISPN-7425 URL: https://issues.jboss.org/browse/ISPN-7425 Project: Infinispan Issue Type: Enhancement Components: Console Affects Versions: 9.0.0.Beta2 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 9.0.0.CR1 We need to add the ability to remove configuration subsections (locking, expiration etc) and make it consistent across configuration screens. UI perspective: We could have a delete icon (red cross or trash can etc) in the "panel-title" div of the section that a user is editing. If the user chooses to delete this sections config, then they should be presented with a message screen saying "<section> has not been defined, would you like to define this now?" similar to how we ask users to define container security when they click on the security section. Similarly, if a user loads an existing config with a section undefined, the aforementioned message should be displayed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2017