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


   ## What is the purpose of the change
   
   This change shall enable us to return different data types instead of only 
returning Strings for the cluster configuration endpoint. We use this feature 
to return long instead of String for memory-related configuration entries. This 
will make it possible to convert the corresponding values into human-readable 
values.
   
   ## Brief change log
   
   * A generic type is added to `ClusterConfigurationInfoEntry` specifying the 
value's data type.
   * A new factory method 
`ClusterConfigurationInfo.createClusterConfigurationInfoEntry` for creating 
entries is introduced that applies custom creation logic for memory-related 
parameters and falling back to the default approach for any other parameter.
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
   * `ClusterConfigurationInfoTest` was adapted accordingly adding more test 
cases
   * `YARNSessionCapacitySchedulerITCase` needed a small refactoring to adapt 
to the change
   
   ## 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? no
     - If yes, how is the feature documented? not applicable
   


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