[IGNITE-12825] Serialize Java and .NET dates using same calendars

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.8
• Fix Version/s: 3.0
• Component/s: platforms
• Labels: .NET ignite-3 sbcf
• Release Note: Will be fixed by IGNITE-12824
• Assignee: Alexey Kukushkin
• Reporter: Alexey Kukushkin
• Created: 22/Mar/20 21:33
• Updated: 03/Nov/20 20:47
• Resolved: 03/Nov/20 20:46

Description

Java and .NET use different calendars for dates serialization. That results in some dates written using Java API deserialized into different dates using .NET API and vise versa. For example, 1-Jan-1992 00:00:00 MSK written using Java API will be read as 31-Dec-1991 1:00:00 MSK using .NET API. 

Java and .NET API must use same calendars for dates serialization.

Note:

Java uses IANA Time Zone database (https://www.iana.org/time-zones) stored locally that could be manually updated using Timezone Updater Tool (https://www.oracle.com/technetwork/java/javase/documentation/tzupdater-readme-136440.html)

.NET uses its own calendars that cannot be manually updated. 

For all the Java/.NET calendar differences I saw the Java version was valid and .NET version was not.

We need to use IANA time zone database in .NET as well and, if possible, provide a mechanism to update the time zone database

Issue Links

• is blocked by: IGNITE-12824 .NET: Interoperable DateTime
• is related to: IGNITE-12859 .NET: Services fail to call method with DateTime or Guid argument
• links to: GitHub Pull Request #7617