[ 
https://issues.apache.org/jira/browse/GEODE-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478758#comment-17478758
 ] 

ASF GitHub Bot commented on GEODE-9968:
---------------------------------------

gaussianrecurrence opened a new pull request #910:
URL: https://github.com/apache/geode-native/pull/910


    - Solved addition of attributes for previously defined PdxSerializable
      implementations, which was not working before.
    - Added a new IT to verify that it's possible to add a new attribute
      under all scenarios.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


> Fix deserialization for new fields in PdxSerializable class
> -----------------------------------------------------------
>
>                 Key: GEODE-9968
>                 URL: https://issues.apache.org/jira/browse/GEODE-9968
>             Project: Geode
>          Issue Type: Bug
>          Components: native client
>            Reporter: Mario Salazar de Torres
>            Assignee: Mario Salazar de Torres
>            Priority: Major
>              Labels: needsTriage
>
> *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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to