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

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

    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

          blocks

          Sub-task - The sub-task of the issue IGNITE-2398 .NET: Change default mapper behavior

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-1894 .NET: Delegate support in the API via extension methods

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-3689 .NET: Remove IgniteProxy

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-4669 .NET: Sort binary object fields

          • Major - Major loss of function.
          • Resolved

          Task - A task that needs to be done. IGNITE-4498 .NET: Remove legacy BinaryObject.Equals

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-4614 .NET: Binary schema is not reset in BinaryReader

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-4592 .NET: Binary enums are handled incorrectly

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-4663 BinaryUtils.doReadObjectArray can not read array with platform-only element type

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-4673 Object array element type is written as a user type

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-2843 .NET: CacheConfiguration.WriteThrough/ReadThrough properties are missing

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-4157 Use discovery custom messages instead of marshaller cache

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-3796 .NET: Platforms system cache

          • Major - Major loss of function.
          • Closed
          Is contained by

          Task - A task that needs to be done. IGNITE-4547 Apache Ignite 2.0 quick and needed tasks

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is related to

          New Feature - A new feature of the product, which has yet to be developed. IGNITE-2492 .NET: Peer assembly loading

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-2746 .NET: Improve ReflectiveSerializer control with attributes

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          relates to

          New Feature - A new feature of the product, which has yet to be developed. IGNITE-2826 .NET: Write DataContract types as binary

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-2827 .NET: Write XmlSerializer types as binary

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-2825 .NET: Write Serializable as binary

          • Major - Major loss of function.
          • Resolved
          supercedes

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-3734 .NET: Throw an exception when user tries to run SQL over [Serializable] types

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Web Link GitHub Pull Request #1664

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: