July 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6773) Metadata updates get dropped with Functional API

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6773?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6773: -------------------------------------- Fix Version/s: 9.0.0.Alpha3 > Metadata updates get dropped with Functional API > ------------------------------------------------ > > Key: ISPN-6773 > URL: https://issues.jboss.org/browse/ISPN-6773 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Alpha2, 8.2.2.Final > Reporter: Krzysztof Sobolewski > Fix For: 9.0.0.Alpha3 > > > I have a CacheLoader that injects EmbeddedMetadata so that I can specify the lifetime of the newly loaded entry. EmbeddedMetadata is supposed to be used when only lifespan or maxIdle are required (I only need lifespan); this works because the lifespan (and maxIdle) information is copied into the internal node itself - no extra Metadata object is allocated. > The InternalNode has several implementations, each used for the different combination of lifespan and maxIdle. Let's proceed with MortalCacheEntry (lifespan only). Its metadata-aware sibling is MetadataMortalCacheEntry. Each of those has a special code path in EntryWrappingInterceptor for updates of metadata. This path is chosen not based on the type of the InternalEntry (so that it can also work for new entries, where there's no internal entry object yet) but instead the decision is made in InternalEntryFactoryImpl.isStoreMetadata() based on the type of the Metadata object - if it returns true, then the path for MetadataMortalCacheEntry is used. This path then inspects the actual type of the internal entry object so that can update it accordingly. > Enter Functional API. > After I return EmbeddedMetadata from the CacheLoader, the expiration parameters are updated just fine - the EmbeddedMetadata is recognized and a MortalCacheEntry is created with the expected lifespan. Then, when we use {code:java}EntryView.WriteEntryView.set(value, params...){code} to update the metadata (which is the only way to do that in Functional API), the Metadata object in the entry gets replaced with an instance of MetaParamsInternalMetadata. This makes isStoreMetadata() return true (because the Metadata object is no longer EmbeddedMetadata). EntryWrappingInterceptor then goes into the metadata-aware code path where MortalCacheEntry is not handled (MetadataMortalCacheEntry is instead) and the metadata update is not performed at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6773) Metadata updates get dropped with Functional API

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6773?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-6773: ----------------------------------------- Assignee: Krzysztof Sobolewski > Metadata updates get dropped with Functional API > ------------------------------------------------ > > Key: ISPN-6773 > URL: https://issues.jboss.org/browse/ISPN-6773 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Alpha2, 8.2.2.Final > Reporter: Krzysztof Sobolewski > Assignee: Krzysztof Sobolewski > Fix For: 9.0.0.Alpha3 > > > I have a CacheLoader that injects EmbeddedMetadata so that I can specify the lifetime of the newly loaded entry. EmbeddedMetadata is supposed to be used when only lifespan or maxIdle are required (I only need lifespan); this works because the lifespan (and maxIdle) information is copied into the internal node itself - no extra Metadata object is allocated. > The InternalNode has several implementations, each used for the different combination of lifespan and maxIdle. Let's proceed with MortalCacheEntry (lifespan only). Its metadata-aware sibling is MetadataMortalCacheEntry. Each of those has a special code path in EntryWrappingInterceptor for updates of metadata. This path is chosen not based on the type of the InternalEntry (so that it can also work for new entries, where there's no internal entry object yet) but instead the decision is made in InternalEntryFactoryImpl.isStoreMetadata() based on the type of the Metadata object - if it returns true, then the path for MetadataMortalCacheEntry is used. This path then inspects the actual type of the internal entry object so that can update it accordingly. > Enter Functional API. > After I return EmbeddedMetadata from the CacheLoader, the expiration parameters are updated just fine - the EmbeddedMetadata is recognized and a MortalCacheEntry is created with the expected lifespan. Then, when we use {code:java}EntryView.WriteEntryView.set(value, params...){code} to update the metadata (which is the only way to do that in Functional API), the Metadata object in the entry gets replaced with an instance of MetaParamsInternalMetadata. This makes isStoreMetadata() return true (because the Metadata object is no longer EmbeddedMetadata). EntryWrappingInterceptor then goes into the metadata-aware code path where MortalCacheEntry is not handled (MetadataMortalCacheEntry is instead) and the metadata update is not performed at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6836) Remove references to deprecated Hibernate Search annotation: @ProvidedId

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6836?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-6836: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4445 > Remove references to deprecated Hibernate Search annotation: @ProvidedId > ------------------------------------------------------------------------ > > Key: ISPN-6836 > URL: https://issues.jboss.org/browse/ISPN-6836 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Trivial > Fix For: 9.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6836) Remove references to deprecated Hibernate Search annotation: @ProvidedId

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6836?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-6836: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 > Remove references to deprecated Hibernate Search annotation: @ProvidedId > ------------------------------------------------------------------------ > > Key: ISPN-6836 > URL: https://issues.jboss.org/browse/ISPN-6836 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Trivial > Fix For: 9.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6840) Consider using Dogen

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6840?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-6840: ----------------------------------------- Assignee: Sebastian Łaskawiec > Consider using Dogen > -------------------- > > Key: ISPN-6840 > URL: https://issues.jboss.org/browse/ISPN-6840 > Project: Infinispan > Issue Type: Sub-task > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6839) Move domain setup from Gustavo's repository

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6839?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-6839: ----------------------------------------- Assignee: Gustavo Fernandes (was: Sebastian Łaskawiec) > Move domain setup from Gustavo's repository > ------------------------------------------- > > Key: ISPN-6839 > URL: https://issues.jboss.org/browse/ISPN-6839 > Project: Infinispan > Issue Type: Sub-task > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Gustavo Fernandes > > Repository with Domain Mode: https://github.com/gustavonalle/infinispan-server-domain-docker -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6838) Create an experimental brach for Infinispan 9

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6838?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-6838: ----------------------------------------- Assignee: Sebastian Łaskawiec > Create an experimental brach for Infinispan 9 > --------------------------------------------- > > Key: ISPN-6838 > URL: https://issues.jboss.org/browse/ISPN-6838 > Project: Infinispan > Issue Type: Sub-task > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6839) Move domain setup from Gustavo's repository

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6839?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6839: -------------------------------------- Description: Repository with Domain Mode: https://github.com/gustavonalle/infinispan-server-domain-docker > Move domain setup from Gustavo's repository > ------------------------------------------- > > Key: ISPN-6839 > URL: https://issues.jboss.org/browse/ISPN-6839 > Project: Infinispan > Issue Type: Sub-task > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > > Repository with Domain Mode: https://github.com/gustavonalle/infinispan-server-domain-docker -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6839) Move domain setup from Gustavo's repository

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6839?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-6839: ----------------------------------------- Assignee: Sebastian Łaskawiec > Move domain setup from Gustavo's repository > ------------------------------------------- > > Key: ISPN-6839 > URL: https://issues.jboss.org/browse/ISPN-6839 > Project: Infinispan > Issue Type: Sub-task > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > Repository with Domain Mode: https://github.com/gustavonalle/infinispan-server-domain-docker -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6841) Make startup script configurable (domain/standalone mode, jgroups stack)

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6841: ----------------------------------------- Summary: Make startup script configurable (domain/standalone mode, jgroups stack) Key: ISPN-6841 URL: https://issues.jboss.org/browse/ISPN-6841 Project: Infinispan Issue Type: Sub-task Reporter: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2016