[JBoss JIRA] (ISPN-11981) Stale immortal entry metadata
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11981?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11981:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8453
> Stale immortal entry metadata
> -----------------------------
>
> Key: ISPN-11981
> URL: https://issues.redhat.com/browse/ISPN-11981
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 11.0.0.CR1, 10.1.8.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> When an entry is updated, {{InternalEntryFactoryImpl}} tries to reuse the existing {{InternalCacheEntry}} instance instead of creating a new one. The condition is that both the new and the old entry have the same implementation implementation: immortal, immortal w/ external metadata, transient, transient w/ metadata etc.
> Because {{MetadataImmortalCacheEntry}} extends {{ImmortalCacheEntry}}, that logic is broken: when an immortal entry with external metadata is replaced with a new entry without external metadata, the external metadata is not removed.
> This impacts the anchored keys module, which I am changing to store the key location in the metadata (currently it is stored as a value, and it is broken with BINARY/OFF_HEAP storage). When a node leaves and an entry located on the leaver is updated, the key is written on the newest joiner. The joiner already has a local entry with {{RemoteMetadata}}, and is trying to write a value without any metadata.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (IPROTO-142) Make some fields in bank.proto @SortableField
by Gustavo Fernandes (Jira)
Gustavo Fernandes created IPROTO-142:
----------------------------------------
Summary: Make some fields in bank.proto @SortableField
Key: IPROTO-142
URL: https://issues.redhat.com/browse/IPROTO-142
Project: Infinispan ProtoStream
Issue Type: Bug
Reporter: Gustavo Fernandes
As on-demand field uninverting is not going to be supported in the next Infinispan version, align the bank.proto fields with its usage in the Infinispan test suite.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11986) Resolve unqualified type names in queries
by Nistor Adrian (Jira)
Nistor Adrian created ISPN-11986:
------------------------------------
Summary: Resolve unqualified type names in queries
Key: ISPN-11986
URL: https://issues.redhat.com/browse/ISPN-11986
Project: Infinispan
Issue Type: Enhancement
Components: Embedded Querying, Remote Querying
Reporter: Nistor Adrian
Assignee: Nistor Adrian
Fix For: 12.0.0.Final
When type names are known in advance (indexed cache) we should be able to resolve non-FQN name in queries. We should allow such queries if the name can be resolved unambiguously.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months