[
https://issues.apache.org/jira/browse/FLINK-27930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550860#comment-17550860
]
Gyula Fora commented on FLINK-27930:
------------------------------------
It might be in String type in the JobStatus but in other places like
SavepointInfo, ReconciliationStatus the timestamp is in a long field.
I think it only makes everything confusing if we mix different formats within
the status. Because of this I would prefer to keep it as is.
> 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)
