[
https://issues.apache.org/jira/browse/IGNITE-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010107#comment-16010107
]
Pavel Tupitsyn commented on IGNITE-5207:
----------------------------------------
[~vozerov] no changes to the protocol.
* Enums can be {{byte}}, {{sbyte}}, {{short}}, {{ushort}}, {{int}}, {{uint}},
{{long}}, {{ulong}}.
* In 2.0 there is an exception for any non-Int32 enum.
* After this fix all enums that fit into 4 bytes are written in Ignite format.
{{long}} and {{ulong}} enums are written as regular objects with a single field
(via reflective serializer).
> .NET: Non-Int32 enums can't be serialized
> -----------------------------------------
>
> Key: IGNITE-5207
> URL: https://issues.apache.org/jira/browse/IGNITE-5207
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Affects Versions: 2.0
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> There is no way to serialize non-Int32 enums.
> Enums in .NET can be {{byte}}, {{sbyte}}, {{short}}, {{ushort}}, {{int}},
> {{uint}}, {{long}}, {{ulong}} (see
> https://docs.microsoft.com/en-us/dotnet/articles/csharp/language-reference/keywords/enum).
> We should write all of these except {{long}} and {{ulong}} properly
> (converting them to int and back).
> {{long}} and {{ulong}} enums should be written as object.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
