[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
2 months
[JBoss JIRA] (ISPN-6889) Create directive for generic field form groups
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-6889?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-6889:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/119
> Create directive for generic field form groups
> ----------------------------------------------
>
> Key: ISPN-6889
> URL: https://issues.jboss.org/browse/ISPN-6889
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 9.0.0.Alpha3
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
>
> We should be able to significantly reduce the amount of duplicate code if we create a directive for handling generic fields that are found across the console. Where a generic field consists of a label, input field, tooltip and undo/restart required fields. Currently the logic for these fields is repeated, in some cases with small variations, across multiple directives.
> It should be possible to create a directive that takes in the appropriate metadata,prevData and data objects for a specified field and handles the setting/unsetting of style data internally within the new directive.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (ISPN-6889) Create directive for generic field form groups
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-6889?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-6889:
-------------------------------
Status: Open (was: New)
> Create directive for generic field form groups
> ----------------------------------------------
>
> Key: ISPN-6889
> URL: https://issues.jboss.org/browse/ISPN-6889
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 9.0.0.Alpha3
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
>
> We should be able to significantly reduce the amount of duplicate code if we create a directive for handling generic fields that are found across the console. Where a generic field consists of a label, input field, tooltip and undo/restart required fields. Currently the logic for these fields is repeated, in some cases with small variations, across multiple directives.
> It should be possible to create a directive that takes in the appropriate metadata,prevData and data objects for a specified field and handles the setting/unsetting of style data internally within the new directive.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months