[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
5 days, 14 hours
[JBoss JIRA] (ISPN-10262) Deprecate custom interceptors configuration
by Dan Berindei (Jira)
Dan Berindei created ISPN-10262:
-----------------------------------
Summary: Deprecate custom interceptors configuration
Key: ISPN-10262
URL: https://issues.jboss.org/browse/ISPN-10262
Project: Infinispan
Issue Type: Task
Components: Configuration, Core
Affects Versions: 10.0.0.Beta3
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 10.0.0.Beta4
The custom interceptors support puts very hard limits on the changes we can make to our interceptors, because almost any change to our interceptors, the commands, or the invocation context will require changes to the user-defined custom interceptors as well.
We will keep the support for modules and tests to add new interceptors, but it will no longer be part of the public API and the configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 4 months
[JBoss JIRA] (ISPN-10262) Deprecate custom interceptors configuration
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-10262?page=com.atlassian.jira.plugin... ]
Dan Berindei updated ISPN-10262:
--------------------------------
Status: Open (was: New)
> Deprecate custom interceptors configuration
> -------------------------------------------
>
> Key: ISPN-10262
> URL: https://issues.jboss.org/browse/ISPN-10262
> Project: Infinispan
> Issue Type: Task
> Components: Configuration, Core
> Affects Versions: 10.0.0.Beta3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Beta4
>
>
> The custom interceptors support puts very hard limits on the changes we can make to our interceptors, because almost any change to our interceptors, the commands, or the invocation context will require changes to the user-defined custom interceptors as well.
> We will keep the support for modules and tests to add new interceptors, but it will no longer be part of the public API and the configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 4 months