You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/04/10 15:11:51 UTC

[GitHub] [flink] zjffdu opened a new pull request #8144: [FLINK-12159]. Enable YarnMiniCluster integration test under non-secure mode

zjffdu opened a new pull request #8144: [FLINK-12159]. Enable YarnMiniCluster integration test under non-secure mode
URL: https://github.com/apache/flink/pull/8144
 
 
   ## What is the purpose of the change
   I can not run flink in YarnMiniCluster for integration test because yarn-site.xml is not shipped to yarn container (krb5Config must be non-empty otherwise yarn-site.xml won't been shipped). It doesn't make sense to to only allow yarn integration under secure mode. So this PR just try to enable YarnMiniCluster integration test under non-secure mode. I tested this PR for zeppelin flink integration test.
   
   
   ## Brief change log
   
   Straightforward code refactoring to separate `yarn-site.xml` and `krb5Config` file.
   
   
   ## Verifying this change
   
   *(Please pick either of the following options)*
   
   This change is a trivial rework / code cleanup without any test coverage.
   I verified this PR in zeppelin flink integration test.
   
   
   ## 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, 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:
users@infra.apache.org


With regards,
Apache Git Services