You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Luke Cwik (Jira)" <ji...@apache.org> on 2019/09/06 03:13:00 UTC

[jira] [Commented] (BEAM-5530) Migrate to java.time lib instead of joda-time

    [ https://issues.apache.org/jira/browse/BEAM-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923892#comment-16923892 ] 

Luke Cwik commented on BEAM-5530:
---------------------------------

One advantage with jodatime is that the TZDB is typically updated more often and you don't have to wait for a JVM release or muck with the JVM installation to get an update TZDB.

Once custom containers are used for the Java SDK everywhere, this point will be moot because then anybody will be able to roll their own container containing an updated TZDB,

> Migrate to java.time lib instead of joda-time
> ---------------------------------------------
>
>                 Key: BEAM-5530
>                 URL: https://issues.apache.org/jira/browse/BEAM-5530
>             Project: Beam
>          Issue Type: Improvement
>          Components: dependencies
>            Reporter: Alexey Romanenko
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Joda-time has been used till moving to Java 8. For now, these two time libraries are used together. It will make sense finally to move everywhere to only one lib - *java.time* - as a standard Java time library (see mail list discussion: [https://lists.apache.org/thread.html/b10f6f9daed44f5fa65e315a44b68b2f57c3e80225f5d549b84918af@%3Cdev.beam.apache.org%3E]).
>  
> Since this migration will introduce breaking API changes, then we should address it to 3.0 release.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)