回复：Codespeed deployment for Flink

Thanks @Piotr Nowojski and @Nico Kruber for the good job! I already benefit from this benchmark in the previous PRs. Wish the visualization tool becoming stronger to benefit more for the community! Best, Zhijiang -- 发件人：Piotr Nowoj

[jira] [Created] (FLINK-10413) requestPartitionState messages overwhelms JM RPC main thread

Zhu Zhu created FLINK-10413: --- Summary: requestPartitionState messages overwhelms JM RPC main thread Key: FLINK-10413 URL: https://issues.apache.org/jira/browse/FLINK-10413 Project: Flink Issue Typ

[jira] [Created] (FLINK-10412) toString field in AbstractID should be transient to avoid been serialized

Zhu Zhu created FLINK-10412: --- Summary: toString field in AbstractID should be transient to avoid been serialized Key: FLINK-10412 URL: https://issues.apache.org/jira/browse/FLINK-10412 Project: Flink

Re: [DISCUSS] [Contributing] (2) - Review Steps

Thanks for start the discussion Stephan! (1) Do we agree on the five basic steps below?* +1 to the five steps and making the third question in the proposal the first. (2) How do we understand that consensus is reached about adding the feature? +1 to lazy consensus with one committer's +1 (3) To

[jira] [Created] (FLINK-10411) Make ClusterEntrypoint more modular

Till Rohrmann created FLINK-10411: - Summary: Make ClusterEntrypoint more modular Key: FLINK-10411 URL: https://issues.apache.org/jira/browse/FLINK-10411 Project: Flink Issue Type: Improvement

Re: [DISCUSS] [Contributing] (3) - Review Tooling

Hi, Coming back to the original topic of the thread: How to implement the guided review process. I am in favor of starting with a low-tech solution. We design a review template with a checkbox for the five questions (see [1]) and a link to the detailed description of the review process ([1] will

Re: [DISCUSS] [Contributing] (2) - Review Steps

Thanks for separating the threads Stephan! (1) Do we agree on the five basic steps below?* +1 to the five steps and making the third question in the proposal the first. (2) How do we understand that consensus is reached about adding the feature? +1 to lazy consensus with one committer's +1 (3) T

[jira] [Created] (FLINK-10410) Search for broken links on travis

Chesnay Schepler created FLINK-10410: Summary: Search for broken links on travis Key: FLINK-10410 URL: https://issues.apache.org/jira/browse/FLINK-10410 Project: Flink Issue Type: Improve

[jira] [Created] (FLINK-10409) Collection data sink does not propagate exceptions

Dawid Wysakowicz created FLINK-10409: Summary: Collection data sink does not propagate exceptions Key: FLINK-10409 URL: https://issues.apache.org/jira/browse/FLINK-10409 Project: Flink Is

Re: [DISCUSS] [Contributing] (3) - Review Tooling

Hi, About "valuable", I agree with @Aljoscha that there is no clear standard of judgment about "valuable". But I think the priority may be a more specific indicator, because the JIRA issue also has a "Priority" attribute. Maybe we can tag the PR, for example: use the "Label" function of github, or

[ANNOUNCE] Weekly community update #39

Dear community, this is the weekly community update thread #39. Please post any news and updates you want to share with the community to this thread. # Flink 1.6.1 and Flink 1.5.4 released The community has released new bug fix releases: Flink 1.6.1 and Flink 1.5.4 [1, 2]. # Open source review

[jira] [Created] (FLINK-10408) Cannot use window information in Table functions

Alexis Sarda-Espinosa created FLINK-10408: - Summary: Cannot use window information in Table functions Key: FLINK-10408 URL: https://issues.apache.org/jira/browse/FLINK-10408 Project: Flink

[jira] [Created] (FLINK-10407) Reactive container mode

Till Rohrmann created FLINK-10407: - Summary: Reactive container mode Key: FLINK-10407 URL: https://issues.apache.org/jira/browse/FLINK-10407 Project: Flink Issue Type: New Feature C

[jira] [Created] (FLINK-10406) Port JobManagerTest to new code base

tison created FLINK-10406: - Summary: Port JobManagerTest to new code base Key: FLINK-10406 URL: https://issues.apache.org/jira/browse/FLINK-10406 Project: Flink Issue Type: Sub-task Compone

[jira] [Created] (FLINK-10405) Port JobManagerFailsITCase to new code base

tison created FLINK-10405: - Summary: Port JobManagerFailsITCase to new code base Key: FLINK-10405 URL: https://issues.apache.org/jira/browse/FLINK-10405 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-10404) Declarative resource management

Till Rohrmann created FLINK-10404: - Summary: Declarative resource management Key: FLINK-10404 URL: https://issues.apache.org/jira/browse/FLINK-10404 Project: Flink Issue Type: New Feature

Re: [DISCUSS] [Contributing] (3) - Review Tooling

In Beam, we have a bot that regularly nags people about inactive PRs and also closes them after long inactivity. And we use the github feature for assigning reviewers in github. Sometimes it is hard for people to judge how "valuable" a PR is. Maybe some knowledgable people could mark PRs as val

[jira] [Created] (FLINK-10403) Port JobManagerHAProcessFailureBatchRecoveryITCase to new code base

Till Rohrmann created FLINK-10403: - Summary: Port JobManagerHAProcessFailureBatchRecoveryITCase to new code base Key: FLINK-10403 URL: https://issues.apache.org/jira/browse/FLINK-10403 Project: Flink