ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2703) .NET: Dynamically registered classes must use binary serialization if possible.
Date Mon, 25 Jul 2016 16:43:20 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392258#comment-15392258

Pavel Tupitsyn commented on IGNITE-2703:

1) Dynamic registration does not make sense in a cluster with old nodes. These old nodes do
not have new classes anyway, and we do not have peer loading in .NET.
I don't think it's an issue. If the user does not attempt dynamic registration, everything
else will work.

2) Ok, I'll have a look later

3) Fixed

4) I've refactored this a bit to make it clear (moved nullify call to `PlatformDotNetConfigurationClosure.apply0`).
Essentially, work directory that is set in .NET code does not work currently. We use a dir
that is set by temporary marshaller, and there is no way to overwrite it. We should probably
fix this as a separate ticket, but I have no clear idea how exactly. Thoughts?

> .NET: Dynamically registered classes must use binary serialization if possible.
> -------------------------------------------------------------------------------
>                 Key: IGNITE-2703
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2703
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Pavel Tupitsyn
>            Priority: Critical
>              Labels: .net, roadmap
>             Fix For: 1.7
> At present we support dynamic class registration in .NET, but they are written using
deafult .NET mechanism. This is counterintuitive for users and not consistent with Java, where
such classes are written in binary form.
> Proposed implementation plan:
> 1) For each dynamically registered class we must understand whether it could be serialized
through binary or not. If not - print a warning and fallback to .NET.
> 2) Before writing a class we must ensure that it's [typeId -> name] pair is known
to the cluster. If not - write full class name instead of type ID. Java already do that.
> 3) Last, to support backward compatibility we must be able to fallback to current mode
with help of some boolean flag.

This message was sent by Atlassian JIRA

View raw message