flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6437) Move history server configuration to a separate file
Date Mon, 08 Oct 2018 09:40:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641591#comment-16641591

ASF GitHub Bot commented on FLINK-6437:

yanghua 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-427774371
   @StephanEwen @tillrohrmann and @zentol ,Any opinions about 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:

> 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

View raw message