GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/4512

    [FLINK-7408] [conf] Create WebOptions for WebRuntimeMonitor

    ## What is the purpose of the change
    
    This commit moves the WebRuntimeMonitor related configuration options from
    JobManagerOptions to WebOptions. Moreover, it removes the prefix jobmanager.
    
    As you've requested @zentol.
    
    ## Verifying this change
    
    This change is a trivial rework / code cleanup without any test coverage.
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): (no)
      - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes)
      - The serializers: (no)
      - The runtime per-record code paths (performance sensitive): (no)
      - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
    
    ## Documentation
    
      - Does this pull request introduce a new feature? (no)
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tillrohrmann/flink portWebMonitorOptions

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/4512.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4512
    
----
commit 34c0fcb40f9704f6eab6a9cc520e9a27b91ff0d0
Author: Till Rohrmann <trohrm...@apache.org>
Date:   2017-08-10T09:42:09Z

    [FLINK-7408] [conf] Create WebOptions for WebRuntimeMonitor
    
    This commit moves the WebRuntimeMonitor related configuration options from
    JobManagerOptions to WebOptions. Moreover, it removes the prefix jobmanager.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to