[ https://issues.apache.org/jira/browse/IGNITE-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Kukushkin updated IGNITE-12825: -------------------------------------- Ignite Flags: (was: Docs Required,Release Notes Required) > Serialize Java and .NET dates using same calendars > -------------------------------------------------- > > Key: IGNITE-12825 > URL: https://issues.apache.org/jira/browse/IGNITE-12825 > Project: Ignite > Issue Type: Improvement > Components: platforms > Affects Versions: 2.8 > Reporter: Alexey Kukushkin > Assignee: Alexey Kukushkin > Priority: Major > Labels: .NET, ignite-3, sbcf > Fix For: 3.0 > > Attachments: ignite-12825-vs-2.8.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)