[JBoss JIRA] (ISPN-3460) Refactor the CacheEntry hierarchy
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-3460?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-3460:
------------------------------------
I'm not convinced we should have a {{Metadata}} instance every time. Personally I'd rather remove the custom metadata option, e.g. {{cache.put(key, value, new CustomMetadata()}}, and fit everything in the {{CacheEntry}} :)
> Refactor the CacheEntry hierarchy
> ---------------------------------
>
> Key: ISPN-3460
> URL: https://issues.jboss.org/browse/ISPN-3460
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Reporter: Mircea Markus
> Assignee: William Burns
> Priority: Minor
>
> ATM we keep the metadata information in 3 places: CacheValues, CacheEntries and Metadata. We should move everything in the Metadata and make the CacheValues and the CacheEntries reference it.
> Also look at MimeMetadataHelper in REST cache store...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (ISPN-9330) Rewrite Embedded/Remote Compatibility documentation section
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9330?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9330:
------------------------------------
Description:
The section is outdated and compat mode should not be recommended to users.
Accessing data from multiple endpoints is possible without having to resort to store data as java objects.
was:
The section is outdated and compat mode should not be recommended to users.
Accessing data from multiple endpoints is possible without having to resort to store data as java objects
> Rewrite Embedded/Remote Compatibility documentation section
> -----------------------------------------------------------
>
> Key: ISPN-9330
> URL: https://issues.jboss.org/browse/ISPN-9330
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The section is outdated and compat mode should not be recommended to users.
> Accessing data from multiple endpoints is possible without having to resort to store data as java objects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (ISPN-9330) Rewrite Embedded/Remote Compatibility documentation section
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-9330:
---------------------------------------
Summary: Rewrite Embedded/Remote Compatibility documentation section
Key: ISPN-9330
URL: https://issues.jboss.org/browse/ISPN-9330
Project: Infinispan
Issue Type: Enhancement
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
The section is outdated and compat mode should not be recommended to users.
Accessing data from multiple endpoints is possible without having to resort to store data as java objects
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (ISPN-9329) NPE during cache start due to circular component dependencies
by Paul Ferraro (JIRA)
Paul Ferraro created ISPN-9329:
----------------------------------
Summary: NPE during cache start due to circular component dependencies
Key: ISPN-9329
URL: https://issues.jboss.org/browse/ISPN-9329
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.3.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Blocker
Here's the circular dependency:
InternalDataContainerAdapter -> KeyPartitioner -> GroupManager -> DistributionManager -> KeyPartitioner
Seems like this would affect any segmented cache mode using either a custom data container or an off-heap data container.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months