Details
-
Sub-task
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
ignite-1.4
-
None
Description
Currently we always write -1 as enum type ID in .NET. We made this for two reasons:
1) .NET has fair generics and always has necessary type info to perform deserialization.
2) We do not have dynamic portable type register as in Java yet.
However, this approach make it impossible to interoperate with Java when context cannot be inferred. E.g. in queries.
Full solution:
1) Implement dynamic types register.
2) Always pass Enum type ID.
Solution require in scope of this ticket due to tight release schedule:
1) Pass enum type ID when possible, i.e. when enum is restered as portable type explicitly.
Attachments
Issue Links
- blocks
-
IGNITE-1965 .NET: Introduce wrapper for enums, similar to "IBinaryObject".
- Closed
- links to