Re: JIRA Permission Opening Application

Thank you, Weihua. Yes, I have created a new Issue to familiarize myself with the complete process of contribution! > 2023年7月11日 13:37，Weihua Hu 写道： > > ​满帮安全提示: 此封邮件来自公司外部，除非您能判断发件人和知道邮件内容安全，否则请勿打开链接或者附件。 > MB Security Tips: Please do not click on links or open attachments unless you > trust

Re: JIRA Permission Opening Application

Hi YongPing Thank you for your willingness to contribute, no special permissions are required, just find the issue you want to contribute to or create a new one and then you contribute the code, refer to the how-to-contribute[1] [1] https://flink.apache.org/how-to-contribute/contribute-code/ Bes

Re: [DISUCSS] Deprecate multiple APIs in 1.18

Thanks for bringing this up, Matthias. I've replied to you in the other thread[1]. Best, Xintong [1] https://lists.apache.org/thread/l3dkdypyrovd3txzodn07lgdwtwvhgk4 On Mon, Jul 10, 2023 at 8:37 PM Matthias Pohl wrote: > @Xintong did you come across FLINK-3957 [1] when looking for deprecated

Re: [DISCUSS] Release 2.0 Work Items

@Zhu, As you are downgrading "Clarify the scopes of configuration options" to nice-to-have priority, could you also bring that up in the vote thread[1]? I'm asking because there are people who already voted on the original list. I think restarting the vote is probably an overkill and unnecessary, b

[jira] [Created] (FLINK-32573) Translate "Custom Serialization for Managed State" page into Chinese

Yongping Li created FLINK-32573: --- Summary: Translate "Custom Serialization for Managed State" page into Chinese Key: FLINK-32573 URL: https://issues.apache.org/jira/browse/FLINK-32573 Project: Flink

[DISCUSS] FLIP 333 - Redesign Apache Flink website

Hi, I’m opening this thread to discuss a proposal to redesign the Apache Flink website: https://flink.apache.org. The approach and a few initial mockups are included in FLIP 333 - Redesign Apache Flink website.

Re: [DISCUSS] FLIP-327: Support stream-batch unified operator to improve job throughput when processing backlog data

Hi Dong, Thanks for the proposal! The FLIP is already in good shape. I got some NIT questions. 1. It is a little bit weird to write the hint right after the motivation that some features have been moved to FLIP-331, because at that time, readers don't know the context about what features does it

[jira] [Created] (FLINK-32572) Do not collect metrics or scale finished job vertices

Gyula Fora created FLINK-32572: -- Summary: Do not collect metrics or scale finished job vertices Key: FLINK-32572 URL: https://issues.apache.org/jira/browse/FLINK-32572 Project: Flink Issue Type:

Re: [DISCUSS] FLIP-309: Enable operators to trigger checkpoints dynamically

Hi All, Me and Dong chatted offline about the above mentioned issues (thanks for that offline chat I think it helped both of us a lot). The summary is below. > Previously, I thought you meant to add a generic logic in SourceReaderBase > to read existing metrics (e.g. backpressure) and emit the >

[jira] [Created] (FLINK-32571) Prebuild HBase testing docker image

Chesnay Schepler created FLINK-32571: Summary: Prebuild HBase testing docker image Key: FLINK-32571 URL: https://issues.apache.org/jira/browse/FLINK-32571 Project: Flink Issue Type: Techn

Re: [DISCUSS] Release 2.0 Work Items

I brought it up in the deprecating APIs in 1.18 thread [1] already but it feels misplaced there. I just wanted to ask whether someone did a pass over FLINK-3957 [2]. I came across it when going through the release 2.0 feature list [3] as part of the vote. I have the feeling that there are some vali

Re: [DISCUSS] FLIP-325: Support configuring end-to-end allowed latency

Hi, After reading through the discussion, I think the FLIP should provide additional details and explanations about the exact semantics of the end-to-end latency configuration and how it interacts with all other configurations around latency, such as checkpointing. In this context, I have a few

[jira] [Created] (FLINK-32570) Deprecate API that uses Flink's Time implementation (related to FLINK-14638)

Matthias Pohl created FLINK-32570: - Summary: Deprecate API that uses Flink's Time implementation (related to FLINK-14638) Key: FLINK-32570 URL: https://issues.apache.org/jira/browse/FLINK-32570 Projec

Re: [DISCUSS] Release 2.0 Work Items

Agreed that we should deprecate affected APIs as soon as possible. But there is not much time before the feature freeze of 1.18, hence I'm a bit concerned that some of the deprecations might not be done 1.18. We are currently looking into the improvements of the configuration layer. Most of the p

Re: [DISCUSS] FLIP-314: Support Customized Job Lineage Listener

Thanks Shammon for driving this FLIP, I have some comments about the updated FLIP. 1. It confuses for me that LineageEdge interface contains multiple sources but one sink, the relation looks like a graph instead of an edge in topology. 2. TableColumnSourceLineageVertex interface is not clea

Re: [DISUCSS] Deprecate multiple APIs in 1.18

@Xintong did you come across FLINK-3957 [1] when looking for deprecated issues? There are a few subtasks that would require deprecations as well as far as I can see. For some I'm wondering whether we should add them to the release 2.0 feature list [2] in some way and (as a consequence) missed them

Re: [DISCUSS] Release 2.0 Work Items

> > At what point are the FLIP discussions coming into play? I keep wondering if these shouldn't have started already. I think this depends on the responsible contributor and reviewer of individual items. From my perspective, the FLIP discussions can start any time as long as the contributors ar

Re: [DISCUSS] FLIP-325: Support configuring end-to-end allowed latency

Hi Dong, Thanks for the update! Best regards, Jing On Sun, Jul 9, 2023 at 3:26 AM Dong Lin wrote: > Hi Jing, > > Thanks for the suggestions. Please see my reply inline. > > On Fri, Jul 7, 2023 at 3:50 PM Jing Ge wrote: > > > Hi Dong, > > > > Thanks for your clarification. > > > > > > > Actual

[VOTE] Graduate the FileSink to @PublicEvolving

Hi, I'd like to start the VOTE for graduating the FlinkSink to @PublicEvolving. The discussion thread can be found at [1] The vote will be open until at least July 13 12pm GMT(72 hours) unless there is an objection or insufficient votes. Thanks, Jing Ge [1] https://lists.apache.org/thread/wxoo

Re: [VOTE] Release 2.0 must-have work items

+1 On Mon, Jul 10, 2023 at 12:52 PM Yu Li wrote: > +1 (binding) > > Thanks for driving this and great to see us moving forward. > > Best Regards, > Yu > > > On Mon, 10 Jul 2023 at 11:59, Feng Wang wrote: > > > +1 > > Thanks for driving this, looking forward to the next stage of flink. > > > > O

Re: [VOTE] Release 2.0 must-have work items

+1 (binding) Thanks for driving this and great to see us moving forward. Best Regards, Yu On Mon, 10 Jul 2023 at 11:59, Feng Wang wrote: > +1 > Thanks for driving this, looking forward to the next stage of flink. > > On Fri, Jul 7, 2023 at 5:31 PM Xintong Song wrote: > > > Hi all, > > > > I'

[jira] [Created] (FLINK-32569) Fix the incomplete serialization of ResolvedCatalogTable caused by the newly introduced time travel interface

Feng Jin created FLINK-32569: Summary: Fix the incomplete serialization of ResolvedCatalogTable caused by the newly introduced time travel interface Key: FLINK-32569 URL: https://issues.apache.org/jira/browse/FLINK-3

Re: [DISCUSS] Release 2.0 Work Items

At what point are the FLIP discussions coming into play? I keep wondering if these shouldn't have started already. It just seems that a lot of decisions are implicitly reliant on the items even being accepted. Estimates can only be provided if we actually know the scope of the change, but that'

[DISCUSS] FLIP-330: Support specifying record timestamp requirement

Hi all, Dong(cc'ed) and I are opening this thread to discuss our proposal to support optimizing StreamRecord's serialization performance. Currently, a StreamRecord would be converted into a 1-byte tag (+ 8-byte timestamp) + N-byte serialized value during the serialization process. In scenarios wh

Re: [DISCUSS] Release 2.0 Work Items

Hi Matthias, The questions you asked are indeed very important. Here're some quick responses, based on the plans I had in mind, which I have not aligned with other release managers yet. In the previous discussions between the RMs, we were not able to make proposals on things like how to make a ti

[jira] [Created] (FLINK-32568) Ensure that all subtasks are sorted by busy ratio at the backpressure tab by default

Rui Fan created FLINK-32568: --- Summary: Ensure that all subtasks are sorted by busy ratio at the backpressure tab by default Key: FLINK-32568 URL: https://issues.apache.org/jira/browse/FLINK-32568 Project: F

Re: [DISCUSS] Release 2.0 Work Items

Now that the vote is started on the must-have items: There are still to-be-discussed items in the list of features. What's the plan with those? Some of them don't have anyone assigned. Were these items discussed among the release managers? So far, it looks like they are handled as nice-to-have if s