[
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.
Then double check the public methods of {{DateTimeUtils}}, eventually making
some of them private. Some of these methods are used in the planner, where they
should instead use the casting methods. Some of these methods should fail (e.g.
the string to date parsing methods) while at the moment they don't.
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.
Then double check the public methods of {{DateTimeUtils}}, eventually making
some of them private. Some of these methods are used in the planner, where they
should instead use the casting methods.
> 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
> Assignee: 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.
> Then double check the public methods of {{DateTimeUtils}}, eventually making
> some of them private. Some of these methods are used in the planner, where
> they should instead use the casting methods. Some of these methods should
> fail (e.g. the string to date parsing methods) while at the moment they don't.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
