[JBoss JIRA] (ISPN-12289) Anchored keys: skip listener notifications on non-anchor owners
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12289?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12289:
--------------------------------
Description: Anchored keys caches store the value on a single node (the anchor node), and all the other nodes only store a reference to the anchor in a {{RemoteMetadata}} instance. Cluster/client listeners are invoked only once, from the primary owner node, but regular listeners are invoked on all the cache members, even though the value is {{null}}. (was: Anchored keys caches store the value on a single node (the anchor node), and all the other nodes only store a reference to the anchor in a {{RemoteMetadata}} instance. Cluster/client listeners are invoked only once, from the anchor node, but regular listeners are invoked on all the cache members, even though the value is {{null}}.)
> Anchored keys: skip listener notifications on non-anchor owners
> ---------------------------------------------------------------
>
> Key: ISPN-12289
> URL: https://issues.redhat.com/browse/ISPN-12289
> Project: Infinispan
> Issue Type: Bug
> Components: Listeners
> Reporter: Dan Berindei
> Priority: Minor
>
> Anchored keys caches store the value on a single node (the anchor node), and all the other nodes only store a reference to the anchor in a {{RemoteMetadata}} instance. Cluster/client listeners are invoked only once, from the primary owner node, but regular listeners are invoked on all the cache members, even though the value is {{null}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (ISPN-12288) Upgrade to Hibernate Search 6.0.0.Beta10
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12288?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12288:
-------------------------------------
Status: Open (was: New)
> Upgrade to Hibernate Search 6.0.0.Beta10
> ----------------------------------------
>
> Key: ISPN-12288
> URL: https://issues.redhat.com/browse/ISPN-12288
> Project: Infinispan
> Issue Type: Task
> Components: Embedded Querying, Remote Querying
> Affects Versions: 12.0.0.Dev02
> Reporter: Yoann Rodière
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 12.0.0.Dev04
>
> Attachments: javabean-property-access.diff
>
>
> https://in.relation.to/2020/09/07/hibernate-search-6-0-0-Beta10/
> Relevant changes:
> * {{maxDepth}} was renamed to {{includeDepth}}; this may affect the mapping code for Remote Query in particular. PR: https://github.com/hibernate/hibernate-search/pull/2337
> * If Infinispan calls {{SearchResult#totalHitCount()}} anywhere, then it should now call {{total().hitCount()}} instead. {{totalHitCount}} is deprecated.
> * Some SPI interfaces related to the type model have changed and Infinispan implementation may not compile anymore. I recommend changing the Infinispan implementation the same way we changed another mapper bundled with Search (see the attached diff). An added benefit: with these changes, embedded mode will support annotations on both methods and fields (which was supported in 5 but was dropped during the migration to Search 6).
> * {{IndexFieldDescriptor}} now exposes a {{multiValuedInRoot()}} method, which I was told would be very useful to Infinispan, which currently has to go through some hoops to compute that value based on the multi-valued-ness of a field **and its parents**.
> * Timeouts are now forwarded to the entity loader. If Infinispan defines an entity loader when loading hits as entities instead of projections (and it probably should), some changes may be necessary in this area. PR: https://github.com/hibernate/hibernate-search/pull/2333
> Optionally, the new ["total hit count threshold"|https://in.relation.to/2020/09/07/hibernate-search-6-0-0-Beta10/#total-hit-count-threshold] could be used to improve performance in Infinispan, but that should probably be addressed a follow-up ticket.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (ISPN-12289) Anchored keys: skip listener notifications on non-anchor owners
by Dan Berindei (Jira)
Dan Berindei created ISPN-12289:
-----------------------------------
Summary: Anchored keys: skip listener notifications on non-anchor owners
Key: ISPN-12289
URL: https://issues.redhat.com/browse/ISPN-12289
Project: Infinispan
Issue Type: Bug
Components: Listeners
Reporter: Dan Berindei
Anchored keys caches store the value on a single node (the anchor node), and all the other nodes only store a reference to the anchor in a {{RemoteMetadata}} instance. Cluster/client listeners are invoked only once, from the anchor node, but regular listeners are invoked on all the cache members, even though the value is {{null}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (ISPN-8079) QueryInterceptor : Missing value during early rebalance in functional commands
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-8079?page=com.atlassian.jira.plugin... ]
Katia Aresti closed ISPN-8079.
------------------------------
Released prev 12
> QueryInterceptor : Missing value during early rebalance in functional commands
> ------------------------------------------------------------------------------
>
> Key: ISPN-8079
> URL: https://issues.redhat.com/browse/ISPN-8079
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.1.0.Final
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
>
> Functional commands, including ComputeCommand, calculate the value to be set or removed inside the lambda when the command is executing. If the value previous value has to be removed for any reason, the value has to be picked up from the context.
> In some rare cases, during topology changes, the value might not be in the context and so it can't be retrieved or removed. In that particular case, the method provided by the ISPN-7990 issue has to be used to delete the key in every context.
> In this issue, we need to add a reproducer for the problem and correct it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years