You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aitozi (Jira)" <ji...@apache.org> on 2022/06/07 07:14:00 UTC
[jira] [Updated] (FLINK-27930) Format the timestamp in status to make it readable
[ https://issues.apache.org/jira/browse/FLINK-27930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aitozi updated FLINK-27930:
---------------------------
Description:
Currently, the timestamp in status show the unix timestamp, I think we could improve it to an explicit date time
current:
{code:java}
startTime: "1654584619845"
updateTime: "1654585571858" {code}
expect:
{code:java}
startTime: "2022-06-07T06:10:04Z"
updateTime: "2022-06-07T06:50:04Z" {code}
It will follow the k8s's object metadata manner
was:
Currently, the timestamp in status show the unix timestamp, I think we could improve it to a explicit date time
current:
{code:java}
startTime: "1654584619845"
updateTime: "1654585571858" {code}
expect:
{code:java}
startTime: "2022-06-07T06:10:04Z"
updateTime: "2022-06-07T06:50:04Z" {code}
It will follow the k8s's object metadata manner
> Format the timestamp in status to make it readable
> ---------------------------------------------------
>
> Key: FLINK-27930
> URL: https://issues.apache.org/jira/browse/FLINK-27930
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Aitozi
> Priority: Major
>
> Currently, the timestamp in status show the unix timestamp, I think we could improve it to an explicit date time
> current:
> {code:java}
> startTime: "1654584619845"
> updateTime: "1654585571858" {code}
> expect:
> {code:java}
> startTime: "2022-06-07T06:10:04Z"
> updateTime: "2022-06-07T06:50:04Z" {code}
> It will follow the k8s's object metadata manner
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)