[
https://issues.apache.org/jira/browse/FLINK-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901362#comment-15901362
]
ASF GitHub Bot commented on FLINK-5431:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3297
Not sure about this. This seems to implement in Flink what is actually the
responsibility of the logger.
How about just updating the client such that there are two loggers
configured:
1. The one that there is now (all internal stuff)
2. The one that is used for status updates.
The status logger goes to file and console. You can customize the console
logging in the logger config then.
That seems a better separation of concerns, and more generally extensible.
> time format for akka status
> ---------------------------
>
> Key: FLINK-5431
> URL: https://issues.apache.org/jira/browse/FLINK-5431
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Reporter: Alexey Diomin
> Assignee: Anton Solovev
> Priority: Minor
>
> In ExecutionGraphMessages we have code
> {code}
> private val DATE_FORMATTER: SimpleDateFormat = new
> SimpleDateFormat("MM/dd/yyyy HH:mm:ss")
> {code}
> But sometimes it cause confusion when main logger configured with
> "dd/MM/yyyy".
> We need making this format configurable or maybe stay only "HH:mm:ss" for
> prevent misunderstanding output date-time
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
