July 2020 - 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

3 days, 19 hours

2
1
0 / 0

[JBoss JIRA] (ISPN-12181) Report realm readiness through REST login configuration resource

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12181?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12181: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Report realm readiness through REST login configuration resource > ---------------------------------------------------------------- > > Key: ISPN-12181 > URL: https://issues.redhat.com/browse/ISPN-12181 > Project: Infinispan > Issue Type: Enhancement > Components: REST, Security > Affects Versions: 12.0.0.Dev01 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.Dev02 > > > We should add a `ready` boolean to the REST login resource which reports whether the security realm is ready (i.e. it has users) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12004) Add JGroups stack.combine INSERT_BEFORE

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-12004?page=com.atlassian.jira.plugi... ] Ryan Emerson resolved ISPN-12004. --------------------------------- Fix Version/s: 12.0.0.Dev02 (was: 12.0.0.Final) Resolution: Done > Add JGroups stack.combine INSERT_BEFORE > --------------------------------------- > > Key: ISPN-12004 > URL: https://issues.redhat.com/browse/ISPN-12004 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 11.0.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.Dev02 > > > The JGroups stack combiner supports INSERT_AFTER. It is also useful to add INSERT_BEFORE as well as INSERT_ABOVE and INSERT_BELOW aliases to better fit with the JGroups terminology. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12181) Report realm readiness through REST login configuration resource

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12181?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12181: ----------------------------------- Status: Open (was: New) > Report realm readiness through REST login configuration resource > ---------------------------------------------------------------- > > Key: ISPN-12181 > URL: https://issues.redhat.com/browse/ISPN-12181 > Project: Infinispan > Issue Type: Enhancement > Components: REST, Security > Affects Versions: 12.0.0.Dev01 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.Dev02 > > > We should add a `ready` boolean to the REST login resource which reports whether the security realm is ready (i.e. it has users) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12181) Report realm readiness through REST login configuration resource

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12181?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12181: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8601 > Report realm readiness through REST login configuration resource > ---------------------------------------------------------------- > > Key: ISPN-12181 > URL: https://issues.redhat.com/browse/ISPN-12181 > Project: Infinispan > Issue Type: Enhancement > Components: REST, Security > Affects Versions: 12.0.0.Dev01 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.Dev02 > > > We should add a `ready` boolean to the REST login resource which reports whether the security realm is ready (i.e. it has users) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12181) Report realm readiness through REST login configuration resource

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-12181: -------------------------------------- Summary: Report realm readiness through REST login configuration resource Key: ISPN-12181 URL: https://issues.redhat.com/browse/ISPN-12181 Project: Infinispan Issue Type: Enhancement Components: REST, Security Affects Versions: 12.0.0.Dev01 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 12.0.0.Dev02 We should add a `ready` boolean to the REST login resource which reports whether the security realm is ready (i.e. it has users) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11632) Address comments in ISPN-10457

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11632?page=com.atlassian.jira.plugi... ] Ryan Emerson resolved ISPN-11632. --------------------------------- Fix Version/s: 12.0.0.Dev02 (was: 11.0.2.Final) Resolution: Done > Address comments in ISPN-10457 > ------------------------------ > > Key: ISPN-11632 > URL: https://issues.redhat.com/browse/ISPN-11632 > Project: Infinispan > Issue Type: Task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Dev02 > > > There were some late comments in https://github.com/infinispan/infinispan/pull/8096 that we can still address. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12070) Deprecate Marshalling whitelist in favour of allowlist

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-12070?page=com.atlassian.jira.plugi... ] Ryan Emerson resolved ISPN-12070. --------------------------------- Fix Version/s: 12.0.0.Dev02 (was: 12.0.0.Final) Resolution: Done > Deprecate Marshalling whitelist in favour of allowlist > ------------------------------------------------------ > > Key: ISPN-12070 > URL: https://issues.redhat.com/browse/ISPN-12070 > Project: Infinispan > Issue Type: Task > Components: Configuration > Affects Versions: 11.0.1.Final > Reporter: Ryan Emerson > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.Dev02 > > > The {{ClassWhiteList}}, parser, configuration, configuration builders and sys properties all need to be updated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12041) ServerRunMode.FORKED mode doesn't work on Windows

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12041?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12041: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 12.0.0.Dev02 Resolution: Done > ServerRunMode.FORKED mode doesn't work on Windows > ------------------------------------------------- > > Key: ISPN-12041 > URL: https://issues.redhat.com/browse/ISPN-12041 > Project: Infinispan > Issue Type: Task > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Gustavo Lira Silva > Priority: Major > Fix For: 12.0.0.Dev02 > > > Says it all: > > [https://github.com/infinispan/infinispan/blob/master/server/testdriver/co...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-148) Add ProtoField.value() as a convenient alias for number()

by Nistor Adrian (Jira)

Nistor Adrian created IPROTO-148: ------------------------------------ Summary: Add ProtoField.value() as a convenient alias for number() Key: IPROTO-148 URL: https://issues.redhat.com/browse/IPROTO-148 Project: Infinispan ProtoStream Issue Type: Enhancement Affects Versions: 4.4.0.Alpha1 Reporter: Nistor Adrian -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2020