[
https://issues.apache.org/jira/browse/FLINK-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649311#comment-16649311
]
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-429609834
My opinion hasn't changed, I still don't think that it is worth it.
Separating the HistoryServer from your cluster environment is already
trivial: just copy flink-dist to separate locations.
The downside here is you end up with a plethora of unused jars in the
HistoryServer copy, but I'd argue that the HistoryServer shouldn't be bundled
with flink-dist in such a messy way and instead be distributed as a standalone
application. However this shouldn't be discussed in this PR.
----------------------------------------------------------------
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:
[email protected]
> 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)
