Does custom serialization require full deserialization for Sql predicates?

[Jeffrey Yankowski]

Our use case is a Java server application storing data in IHMaps and communicating with a .NET UI (it puts entry listeners on these IHMaps with user defined predicates), so we need our objects in Hazelcast to be platform independent. At the same time, since this is an existing project, we cannot add the Portable interface to our model objects. The goal is to use one serializer for all of our objects, which I was able to accomplish with a Global Serializer. While SQL predicates seem to work with no issues with this global serializer,  does the Hazelcast IMDG have to deserialize all of the objects in the map in order to satisfy the queries? I know for Portable objects it doesn't, but not sure about custom serializers. I'm trying to avoid that because we will have many objects in these maps and deserializing will take a too long for user queries coming from the .NET UI.

[Jeffrey Yankowski]

After doing some research it seems like full deserialization is likely happening for this (confirmation would be great). Compact serialization seems like what I'd want to use to accomplish this, however it doesn't seem to be implemented in C#/.NET yet. It looks like the 5.2 release for that client might come with this serialization functionality. Is there a timeframe on when to expect this release?

[Neil Stevenson]

Hi

 The 5.2 release for .NET is due next month and includes compact serialization.

 If you like, why not join our community slack - https://hazelcastcommunity.slack.com/join/shared_invite/zt-17dltya13-P9pxqzYt_saSe0eEvclDHA#/shared-invite/email

 We'd like to find out more about your querying, as the more we know about what people need, the more we can know which features to build first

Neil

[Jeffrey Yankowski]

Hi Neil,

Thank you for replying back, and that's great to hear that 5.2 is coming to .NET with compact serialization in just a months time. I'll likely look to do a proof of concept implementation upon release. The Java client was quick to put together, so hoping the same will be true for the .NET client.

Thanks,

Jeff