ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Binary object inside Externalizable
Date Sat, 20 Feb 2016 16:59:38 GMT
This would be a difficult issue to solve because of circular references.
Can we in the mean time just make sure that none of Ignite internal objects
are externalizable, so we don’t purposely force this situation onto our
users?

D.

On Fri, Feb 19, 2016 at 7:15 PM, Valentin Kulichenko <
valentin.kulichenko@gmail.com> wrote:

> Folks,
>
> I recently faced an issue which seems to be pretty critical. As you know,
> when binary marshaller meets an Externalizable object, it switches to
> optimized marshaller. And if there is a regular object inside, it's still
> serialized with optimized, even if its type is declared in binary
> configuration with custom mapper, etc. This looks wrong.
>
> It's getting even worse in compute grid, because closure processor wraps
> user's closures in some internal classes, which are Externalizable, so
> these closures are always serialized with optimized marshaller.
>
> Does anyone have ideas on what is the proper fix for this?
>
> -Val
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message