GitHub user nssalian opened a pull request:

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

    FLINK-4402: Wrong metrics parameter names in documentation

    Thanks for contributing to Apache Flink. Before you open your pull request, 
please take the following check list into consideration.
    If your changes take all of the items into account, feel free to open your 
pull request. For more information and/or questions please refer to the [How To 
Contribute guide](http://flink.apache.org/how-to-contribute.html).
    In addition to going through the list, please provide a meaningful 
description of your changes.
    
    - [ ] General
      - JIRA- https://issues.apache.org/jira/browse/FLINK-4402
       - Title: Wrong metrics parameter names in documentation
    
    - [ ] Documentation
      - Changed the task and operator metrics in 
https://ci.apache.org/projects/flink/flink-docs-master/apis/metrics.html to 
align with ConfigConstants.java
    
    - [ ] Tests & Build
      - `mvn clean verify` has been executed successfully locally or a Travis 
build has passed
    


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

    $ git pull https://github.com/nssalian/flink FLINK-4402

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

    https://github.com/apache/flink/pull/2382.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 #2382
    
----
commit 3d22950493abfdb8caae72447bb71bd6fcb8f709
Author: Neelesh Srinivas Salian <nsal...@cloudera.com>
Date:   2016-08-17T18:30:06Z

    FLINK-4402: Changed the documentation for the metrics in the System Scope 
Section

----


---
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