zentol commented on pull request #11839: URL: https://github.com/apache/flink/pull/11839#issuecomment-623436107
I'm currently waiting on more input from the ML before continuing the review. In the mean time, I have an idea on how to solve the issue of stdout/logging going into the same file, and I'm curious whether you think it might work. So far we tried to tackle the problem by changing _where_ the Flink process writes output to (stream redirections), or redirecting the console output (tee). What if the Flink process wouldn't output _anything_ to the console instead writing everything to the files as usual, but we run a separate program that reads back the .out/.log files? Basically, `exec <flink process stuff> | <file reader priting .log/.out files>`. The finicky thing is figuring out which files to read, but we know the names when the process starts, so it should be _feasible_ at least? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
