Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-2703

.NET: Dynamically registered classes must use binary serialization if possible

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ptupitsyn Pavel Tupitsyn
            vozerov Vladimir Ozerov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment