flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [flink] Aitozi opened a new pull request #8479: [FLINK-11193][State Backends]Use user passed configuration overriding default configuration loading from file
Date Sun, 19 May 2019 12:37:34 GMT
Aitozi opened a new pull request #8479: [FLINK-11193][State Backends]Use user passed configuration
overriding default configuration loading from file
URL: https://github.com/apache/flink/pull/8479
 
 
   ## What is the purpose of the change
   
   As described in the [jira](https://issues.apache.org/jira/browse/FLINK-11193), User's customize
configuration which is configured by `backend.configure()` method will be override by the
configuration loading from flink-conf.yaml. I think the config in the code should has a higher
priority than the default file configuration.
   
   ## Brief change log
   
   Merge configuration before create the new state backend.
   
   
   ## Verifying this change
   
   Adding a test case to verify.
   
   This change added tests and can be verified as follows:
   
   *(example:)*
     - *Added integration tests for end-to-end deployment with large payloads (100MB)*
     - *Extended integration test for recovery after master (JobManager) failure*
     - *Added test that validates that TaskInfo is transferred only once across recoveries*
     - *Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers,
a stateful streaming program, and killing one JobManager and two TaskManagers during the execution,
verifying that recovery happens correctly.*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / no)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes
/ no)
     - The serializers: (yes / no / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / no / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing,
Yarn/Mesos, ZooKeeper: (yes / no / don't know)
     - The S3 file system connector: (yes / no / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / no)
     - If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message