[GitHub] StephanEwen commented on issue #6542: [FLINK-6437][History Server] Move history server configuration to a separate file
StephanEwen commented on issue #6542: [FLINK-6437][History Server] Move history server configuration to a separate file URL: https://github.com/apache/flink/pull/6542#issuecomment-412618428 Sure, so the compatibility story needs a more detailed design, and that needs to be discussed before looking at concrete code. Agreed. On whether we want this feature or not - the discussion in Jira was in favor of doing this. Curious what is the reasoning for the push back now, @zentol ? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] StephanEwen commented on issue #6542: [FLINK-6437][History Server] Move history server configuration to a separate file
StephanEwen commented on issue #6542: [FLINK-6437][History Server] Move history server configuration to a separate file URL: https://github.com/apache/flink/pull/6542#issuecomment-412570277 @yanghua You are right, this was not marked as "later" or anything in JIRA. There is never really a time where we don't need to worry about backwards compatibility, so any change that addresses this needs to take this into account. One way to do the backwards compatibility would be to look for the dedicated `flink-historyserver-conf.yaml` config file and fall back to the `flink-conf.yaml` file if the former does not exist. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
