[JBoss JIRA] (ISPN-9695) Add replication counts to xsite
by Pedro Zapata (Jira)
Pedro Zapata created ISPN-9695:
----------------------------------
Summary: Add replication counts to xsite
Key: ISPN-9695
URL: https://issues.jboss.org/browse/ISPN-9695
Project: Infinispan
Issue Type: Feature Request
Components: Cross-Site Replication, JMX, reporting and management
Affects Versions: 9.4.0.Final
Reporter: Pedro Zapata
Assignee: Pedro Ruivo
Fix For: 10.0.0.Alpha1
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (ISPN-9693) Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9693?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9693:
-------------------------------
Sprint: Sprint 10.0.0.Alpha1
> Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
> ---------------------------------------------------------------------------
>
> Key: ISPN-9693
> URL: https://issues.jboss.org/browse/ISPN-9693
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Loaders and Stores
> Affects Versions: 9.4.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Alpha1
>
>
> Currently MarshalledEntryImpl is used throughout both our production and test code. Instead, we should utilise a MarshalledEntryFactory to create all MarshalledEntry instances in production and where appropriate in test classes. Furthermore, we should prevent MarshalledEntryImpl instances being created directly by users.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (ISPN-9693) Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-9693:
----------------------------------
Summary: Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
Key: ISPN-9693
URL: https://issues.jboss.org/browse/ISPN-9693
Project: Infinispan
Issue Type: Enhancement
Components: Core, Loaders and Stores
Affects Versions: 9.4.1.Final
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 10.0.0.Alpha1
Currently MarshalledEntryImpl is used throughout both our production and test code. Instead, we should utilise a MarshalledEntryFactory to create all MarshalledEntry instances in production and where appropriate in test classes. Furthermore, we should prevent MarshalledEntryImpl instances being created directly by users.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (ISPN-9693) Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9693?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9693:
-------------------------------
Status: Open (was: New)
> Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
> ---------------------------------------------------------------------------
>
> Key: ISPN-9693
> URL: https://issues.jboss.org/browse/ISPN-9693
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Loaders and Stores
> Affects Versions: 9.4.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Alpha1
>
>
> Currently MarshalledEntryImpl is used throughout both our production and test code. Instead, we should utilise a MarshalledEntryFactory to create all MarshalledEntry instances in production and where appropriate in test classes. Furthermore, we should prevent MarshalledEntryImpl instances being created directly by users.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (ISPN-9621) Split global marshaller into Persistence and Internal marshaller
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9621?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9621:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6240
> Split global marshaller into Persistence and Internal marshaller
> ----------------------------------------------------------------
>
> Key: ISPN-9621
> URL: https://issues.jboss.org/browse/ISPN-9621
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core, Loaders and Stores
> Affects Versions: 9.4.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Alpha1
>
>
> Currently the internal marshaller is used for marshalling key/value/metadata in store implementations. This means that it is possible for internal classes to be marshalled to a user store, which can cause compatibility issues if an internal classes serialization format changes (due to marshaller changes or addition/removal of fields).
> We should separate the internal and persistence marshaller, only exposing the latter to stores via the InitializationContext. The persistence marshaller should only be able to serialize user key/values and the metadata/version data.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (ISPN-9621) Split global marshaller into Persistence and Internal marshaller
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9621?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9621:
-------------------------------
Status: Open (was: New)
> Split global marshaller into Persistence and Internal marshaller
> ----------------------------------------------------------------
>
> Key: ISPN-9621
> URL: https://issues.jboss.org/browse/ISPN-9621
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core, Loaders and Stores
> Affects Versions: 9.4.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Alpha1
>
>
> Currently the internal marshaller is used for marshalling key/value/metadata in store implementations. This means that it is possible for internal classes to be marshalled to a user store, which can cause compatibility issues if an internal classes serialization format changes (due to marshaller changes or addition/removal of fields).
> We should separate the internal and persistence marshaller, only exposing the latter to stores via the InitializationContext. The persistence marshaller should only be able to serialize user key/values and the metadata/version data.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month