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/06/18 04:08:02 UTC

[GitHub] [flink] godfreyhe opened a new pull request #8772: [FLINK-12878] [travis] Move flink-table-planner-blink/flink-table-runtime-blink to separate profile

godfreyhe opened a new pull request #8772: [FLINK-12878] [travis] Move flink-table-planner-blink/flink-table-runtime-blink to separate profile
URL: https://github.com/apache/flink/pull/8772
 
 
   
   ## What is the purpose of the change
   
   *Move flink-table-planner-blink/flink-table-runtime-blink to separate profile*
   
   
   ## Brief change log
   
     - *Move flink-table-planner-blink/flink-table-runtime-blink to separate profile.
   The flink-table-planner-blink module and flink-table-runtime-blink module take almost 30 minutes, and that may cause libraries profile frequently hits timeouts; we can resolve this by moving flink-table-planner-blink and flink-table-runtime-blink into a separate profile.*
   
   
   ## Verifying this change
   
   This change is a trivial rework without any test coverage.
   
   ## 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