[GEODE-9968] Fix deserialization for new fields in PdxSerializable class

• Type: Bug
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Component/s: native client
• Labels: pull-request-available
• Assignee: Mario Salazar de Torres
• Reporter: Mario Salazar de Torres
• Created: 17/Jan/22 11:17
• Updated: 10/May/22 14:13

Description

GIVEN an implementation of a PdxSerializable class
WHEN a set of entries have been written for this class
AND after a while, the implementation changes, adding new fields
AND a new set of entries are written containing some of the added fields
AND all of the region entries are read
THEN added fields of the latest entries are empty or contain garbage instead

---

Additional information. After analyzing Java implementation for PdxSerializable deserialization, it seems that the client fetches the PdxFields from the remote PdxType, but instead for the C++ implementation, code is different as it uses a mapping called "Local2Remote" (which I suppose it's an optimization). And the current use of this "Local2Remote" mapping is not working correctly under the described scenario.

Issue Links

• links to: GitHub Pull Request #910