philippemarcelino commented on issue #2062:
URL: https://github.com/apache/fury/issues/2062#issuecomment-2706942349
Hi,
Using version 0.10.0, I still experience this issue when the map has a null
value on its "last" element (order as returned by map.entrySet().iterator()). I
encountered this issue with large and complex objects, but it's quite easy to
reproduce, at least on my dev env:
`
// OK (assuming a is the "last" element)
Map<String, Object> map = new HashMap<>();
map.put("a", null);
map.put("b", 1.0);
fury.deserialize(fury.serialize(map));
// OK (same test, just a different map implementation and value object
type)
map = new LinkedHashMap<>();
map.put("a", null);
map.put("b", "One");
fury.deserialize(fury.serialize(map));
// KO (all values set to null)
map = new HashMap<>();
map.put("a", null);
map.put("b", null);
fury.deserialize(fury.serialize(map));
// KO ("last" element value is null)
map = new LinkedHashMap<>();
map.put("a", 1.0);
map.put("b", null);
fury.deserialize(fury.serialize(map));
`
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
