You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Francesco Guardiani (Jira)" <ji...@apache.org> on 2021/10/28 15:40:00 UTC

[jira] [Updated] (FLINK-24507) Cleanup all the various date/time/timestamp utils

     [ https://issues.apache.org/jira/browse/FLINK-24507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Guardiani updated FLINK-24507:
----------------------------------------
    Description: 
There are different timestamp utils that won't be required anymore once FLINK-21456 is solved. For example:

* {{org.apache.flink.table.util.TimestampStringUtils}}
* {{org.apache.flink.table.utils.TimestampStringUtils}}

Double check all the usages of these classes, and if there are any eventual classes like that, and replace them with the new {{DateTimeUtils}} in common whenever is possible

  was:
There are different timestamp utils that won't be required anymore once FLINK-21456 is solved. For example:

* {{org.apache.flink.table.util.TimestampStringUtils}}
* {{org.apache.flink.table.utils.TimestampStringUtils}}

Double check all the usages of these classes, and if there are any eventual classes like that, and replace them with the new {DateTimeUtils} in common whenever is possible


> Cleanup all the various date/time/timestamp utils
> -------------------------------------------------
>
>                 Key: FLINK-24507
>                 URL: https://issues.apache.org/jira/browse/FLINK-24507
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Francesco Guardiani
>            Priority: Major
>
> There are different timestamp utils that won't be required anymore once FLINK-21456 is solved. For example:
> * {{org.apache.flink.table.util.TimestampStringUtils}}
> * {{org.apache.flink.table.utils.TimestampStringUtils}}
> Double check all the usages of these classes, and if there are any eventual classes like that, and replace them with the new {{DateTimeUtils}} in common whenever is possible



--
This message was sent by Atlassian Jira
(v8.3.4#803005)