XComp opened a new pull request #13747:
URL: https://github.com/apache/flink/pull/13747


   ## What is the purpose of the change
   
   We want to expose the JobManager's effective configuration through the 
`/jobmanager/config` REST endpoint. That way, we can expose these values in the 
web UI as it is suggested in 
[FLIP-104](https://cwiki.apache.org/confluence/display/FLINK/FLIP-104%3A+Add+More+Metrics+to+Jobmanager).
   
   ## Brief change log
   
   - Added method to generate dynamic parameters from configuration
   - Added dynamic parameters to BashJavaUtils' JobManager argument extraction 
and integrated the new functionality in multiple script starting the JobManager 
directly or indirectly.
   
   ## Verifying this change
   
   - Added test to JobManagerProcessUtilsTest to check whether the dynamic 
parameter list generation works correctly.
   - Extended BashJavaUtilsITCase to check whether the dynamic properties are 
returned by BashJavaUtilsITCase.
   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)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? yes
     - If yes, how is the feature documented? not documented (the specific 
configuration parameters exposed through the REST endpoint are not documented 
in general)
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to