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

Serialize Java and .NET dates using same calendars

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.8
    • Fix Version/s: 3.0
    • Component/s: platforms
    • Labels:

      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

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              kukushal Alexey Kukushkin
              Reporter:
              kukushal Alexey Kukushkin

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 20m
                20m

                  Issue deployment