You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (Jira)" <ji...@apache.org> on 2020/01/23 00:39:00 UTC
[jira] [Assigned] (GEODE-7735) MemberIdentifierImpl cannot be
deserialized
[ https://issues.apache.org/jira/browse/GEODE-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Smith reassigned GEODE-7735:
--------------------------------
Assignee: Dan Smith
> MemberIdentifierImpl cannot be deserialized
> -------------------------------------------
>
> Key: GEODE-7735
> URL: https://issues.apache.org/jira/browse/GEODE-7735
> Project: Geode
> Issue Type: Bug
> Components: membership
> Reporter: Dan Smith
> Assignee: Dan Smith
> Priority: Major
>
> MemberIdentifierImpl currently implements DataSerializableFixedID, but it has the same DSFID as InternalDistributedMember (DataSerializableFixedID.DISTRIBUTED_MEMBER). When serializables are registered in geode-core, that DataSerializableFixedID.DISTRIBUTED_MEMBER is associated with InternalDistributedMember.
> Currently there is no way to deserialize a MemberIdentifierImpl, because nothing registers DataSerializableFixedID.DISTRIBUTED_MEMBER associated with MemberIdentifierImpl.
> One option might be to have geode-membership register DataSerializableFixedID.DISTRIBUTED_MEMBER with MemberIdentifierImpl and let geode-core override it, but it's probably better not to associate the same ID with two classes. Instead, we should create a new id for MemberIdentifierImpl.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)