rgoers commented on PR #351: URL: https://github.com/apache/flume/pull/351#issuecomment-1299365358
I certainly don't have an issue against providing a Docker image. I just am unclear as to how it will be useful, but I suppose if it is just used as a starting point it could work out. But the approach you mention sounds much better in the long run. I just don't want to have to support that a) I won't have any use for, and b) we will have to keep compatibility with even though we want to do something much better. To be clear, I use the FileChannel, which pretty much requires fast disk (i.e. SSDs or equivalent) to perform well. It also requires a dedicated "disk" so that data isn't lost on restart. This doesn't really work well with Docker/Kubernetes so we don't use it for Flume. -- 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. To unsubscribe, e-mail: dev-unsubscr...@flume.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
