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 2022/07/22 09:56:25 UTC

[GitHub] [flink] dzikosc opened a new pull request, #20344: Flink 23528 fix master

dzikosc opened a new pull request, #20344:
URL: https://github.com/apache/flink/pull/20344

   <!--
   *Thank you very much for contributing to Apache Flink - we are happy that you want to help us improve Flink. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.*
   
   *Please understand that we do not do this to make contributions to Flink a hassle. In order to uphold a high standard of quality for code contributions, while at the same time managing a large number of contributions, we need contributors to prepare the contributions well, and give reviewers enough contextual information for the review. Please also understand that contributions that do not follow this guide will take longer to review and thus typically be picked up with lower priority by the community.*
   
   ## Contribution Checklist
   
     - Make sure that the pull request corresponds to a [JIRA issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no JIRA issue.
     
     - Name the pull request in the form "[FLINK-XXXX] [component] Title of the pull request", where *FLINK-XXXX* should be replaced by the actual issue number. Skip *component* if you are unsure about which is the best component.
     Typo fixes that have no associated JIRA issue should be named following this pattern: `[hotfix] [docs] Fix typo in event time introduction` or `[hotfix] [javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`.
   
     - Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.
     
     - Make sure that the change passes the automated tests, i.e., `mvn clean verify` passes. You can set up Azure Pipelines CI to do that following [this guide](https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository).
   
     - Each pull request should address only one issue, not mix up code from multiple issues.
     
     - Each commit in the pull request has a meaningful commit message (including the JIRA id)
   
     - Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.
   
   
   **(The sections below can be removed for hotfixes of typos)**
   -->
   
   ## What is the purpose of the change
   
   Make necessary changes for KDS connector to survive stop-with-savepoint workflow. Based on:
   https://github.com/apache/flink/pull/17189/ 
   
   ## Brief change log
   
   *   Reenable and harden FlinkKinesisITCase
   *   Fix DataStream#executeAndCollect for stop with savepoint without drain
   *   Avoid another source of interruptions during shutdown of Kinesis consumer
   *   Ensure EFO version of the connector stops gracefully 
   
   
   ## Verifying this change
   
   * All covered by the newly expanded FlinkKinesisITCase
   * EFO scenarios verified locally against custom AWS account and real Kinesis stream
   
   ## 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, Kubernetes/Yarn, 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.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [flink] dannycranmer commented on pull request #20344: Flink 23528 fix master

Posted by GitBox <gi...@apache.org>.
dannycranmer commented on PR #20344:
URL: https://github.com/apache/flink/pull/20344#issuecomment-1193775273

   Related https://github.com/apache/flink/pull/20133
   
   Thanks @dzikosc, LGTM, merging.


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

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [flink] dannycranmer merged pull request #20344: Flink 23528 fix master

Posted by GitBox <gi...@apache.org>.
dannycranmer merged PR #20344:
URL: https://github.com/apache/flink/pull/20344


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

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [flink] flinkbot commented on pull request #20344: Flink 23528 fix master

Posted by GitBox <gi...@apache.org>.
flinkbot commented on PR #20344:
URL: https://github.com/apache/flink/pull/20344#issuecomment-1192403928

   <!--
   Meta data
   {
     "version" : 1,
     "metaDataEntries" : [ {
       "hash" : "0f581d95d66c9b2590b5d4687b81080b9c6a4bb6",
       "status" : "UNKNOWN",
       "url" : "TBD",
       "triggerID" : "0f581d95d66c9b2590b5d4687b81080b9c6a4bb6",
       "triggerType" : "PUSH"
     } ]
   }-->
   ## CI report:
   
   * 0f581d95d66c9b2590b5d4687b81080b9c6a4bb6 UNKNOWN
   
   <details>
   <summary>Bot commands</summary>
     The @flinkbot bot supports the following commands:
   
    - `@flinkbot run azure` re-run the last Azure build
   </details>


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

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org