[
https://issues.apache.org/jira/browse/FLINK-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577910#comment-16577910
]
ASF GitHub Bot commented on FLINK-6437:
---------------------------------------
zentol 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-412430748
I don't think we should do this _now_. It seems like there's little to gain
at this point, since we would still have to support configuration via
`flink-conf.yaml` to not break every existing setup (like this PR does).
Given that there's no overlap between HistoryServer and cluster options
there's also little chance of accidentally messing up the configuration for the
other one.
Besides that this PR is untested (yet again!).
----------------------------------------------------------------
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
> Move history server configuration to a separate file
> ----------------------------------------------------
>
> Key: FLINK-6437
> URL: https://issues.apache.org/jira/browse/FLINK-6437
> Project: Flink
> Issue Type: Improvement
> Components: History Server
> Affects Versions: 1.3.0
> Reporter: Stephan Ewen
> Assignee: vinoyang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
>
> I suggest to keep the {{flink-conf.yaml}} leaner by moving configuration of
> the History Server to a different file.
> In general, I would propose to move configurations of separate, independent
> and optional components to individual config files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
