[jira] [Created] (FLINK-34622) Typo of execution_mode configuration name in Chinese document

Yu Chen created FLINK-34622: --- Summary: Typo of execution_mode configuration name in Chinese document Key: FLINK-34622 URL: https://issues.apache.org/jira/browse/FLINK-34622 Project: Flink Issue Ty

Re: [DISCUSS] FLIP-433: State Access on DataStream API V2

Hi Weijie, Thanks for your answer! Well I get your point. Since partitions are first-class citizens, and redistribution means how states migrate when partitions change, I'd be fine with deemphasizing the concept of keyed/operator state if we highlight the definition of partition in the document. K

Re: [DISCUSS] FLIP-399: Flink Connector Doris

Thanks for the explanation Di Wu. Regards, Jeyhun On Thu, Mar 7, 2024 at 7:48 PM Jing Ge wrote: > Thanks for the clarification. It makes sense to me. > > Best regards, > Jing > > On Wed, Mar 6, 2024 at 10:03 AM wudi <676366...@qq.com.invalid> wrote: > > > Hi Jing Ge, thanks for your suggestions

[jira] [Created] (FLINK-34621) Bump com.google.guava:guava from 31.1-jre to 32.0.0-jre in /flink-connector-hbase-base

Martijn Visser created FLINK-34621: -- Summary: Bump com.google.guava:guava from 31.1-jre to 32.0.0-jre in /flink-connector-hbase-base Key: FLINK-34621 URL: https://issues.apache.org/jira/browse/FLINK-34621

Re: [DISCUSS] FLIP-399: Flink Connector Doris

Thanks for the clarification. It makes sense to me. Best regards, Jing On Wed, Mar 6, 2024 at 10:03 AM wudi <676366...@qq.com.invalid> wrote: > Hi Jing Ge, thanks for your suggestions. > > 1. Currently, the Flink Doris Connector is compatible with Flink versions > 1.15-1.18. SupportsCommitter[1]

Re: [DISCUSS] FLIP-423 ～FLIP-428: Introduce Disaggregated State Storage and Management in Flink 2.0

+1 for Gyula's suggestion. I just finished FLIP-423 which introduced the intention of the big change and high level architecture. Great content btw! The only public interface change for this FLIP is one new config to use ForSt. It makes sense to have one dedicated discussion thread for each concret

[VOTE] FLIP-402: Extend ZooKeeper Curator configurations

Hi everyone, I'd like to start a vote on FLIP-402 [1]. It introduces new configuration options for Apache Flink's ZooKeeper integration for high availability by reflecting existing Apache Curator configuration options. It has been discussed in this thread [2]. I would like to start a vote. The v

[jira] [Created] (FLINK-34620) Process recursive protobuf schemas in PbToRowTypeUtil

Artem created FLINK-34620: - Summary: Process recursive protobuf schemas in PbToRowTypeUtil Key: FLINK-34620 URL: https://issues.apache.org/jira/browse/FLINK-34620 Project: Flink Issue Type: Improveme

[jira] [Created] (FLINK-34619) Do not wait for scaling completion in UPGRADE state with in-place scaling

Gyula Fora created FLINK-34619: -- Summary: Do not wait for scaling completion in UPGRADE state with in-place scaling Key: FLINK-34619 URL: https://issues.apache.org/jira/browse/FLINK-34619 Project: Flink

[jira] [Created] (FLINK-34618) Migrate SplitPythonConditionFromJoinRule

Yongming Zhang created FLINK-34618: -- Summary: Migrate SplitPythonConditionFromJoinRule Key: FLINK-34618 URL: https://issues.apache.org/jira/browse/FLINK-34618 Project: Flink Issue Type: Sub-

[jira] [Created] (FLINK-34617) Correct the Javadoc of org.apache.flink.api.common.time.Time

Yun Tang created FLINK-34617: Summary: Correct the Javadoc of org.apache.flink.api.common.time.Time Key: FLINK-34617 URL: https://issues.apache.org/jira/browse/FLINK-34617 Project: Flink Issue T

Re: [DISCUSS] FLIP-433: State Access on DataStream API V2

Hi Jinzhong, Thanks for the reply! > Overall, I think that the “Eager State Declaration” is a good proposal, which can enhance Flink's state management capabilities and provide possibilities for subsequent state optimizations. It's nice to see that people who are familiar with the state stuff li

[VOTE] Release 1.19.0, release candidate #2

Hi everyone, Please review and vote on the release candidate #2 for the version 1.19.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1],

[jira] [Created] (FLINK-34616) python dist doesn't clean when open method construct resource

Jacky Lau created FLINK-34616: - Summary: python dist doesn't clean when open method construct resource Key: FLINK-34616 URL: https://issues.apache.org/jira/browse/FLINK-34616 Project: Flink Issu

Re: [DISCUSS] FLIP-433: State Access on DataStream API V2

Hi Weijie, Thanks for driving this! 1. Overall, I think that the “Eager State Declaration” is a good proposal, which can enhance Flink's state management capabilities and provide possibilities for subsequent state optimizations. 2. When the user attempts to access an undeclared state at runtime,

Re: [DISCUSS] FLIP-423 ～FLIP-428: Introduce Disaggregated State Storage and Management in Flink 2.0

Hi everyone, Thank you all for a lively discussion here, and it is a good time to move forward to more detailed discussions. Thus we open several threads for sub-FLIPs: FLIP-424: https://lists.apache.org/thread/nmd9qd0k8l94ygcfgllxms49wmtz1864 FLIP-425: https://lists.apache.org/thread/wxn1j848fnf

[DISCUSS] FLIP-427: Disaggregated State Store

Hi devs, I'd like to start a discussion on a sub-FLIP of FLIP-423: Disaggregated State Storage and Management[1], which is a joint work of Yuan Mei, Zakelly Lan, Jinzhong Li, Hangxiang Yu, Yanfei Lei and Feng Wang: - FLIP-427: Disaggregated State Store This FLIP introduces the initial version o

Re: [DISCUSS] FLIP-433: State Access on DataStream API V2

Hi Hangxiang, Thanks for your reply! > We have also discussed in FLIP-359/FLINK-32658 about limiting the user operation to avoid creating state when processElement. Could current interfaces also help this? I think so. It is illegal to create state at runtime in our proposal. > Could you provid

Re: Default scale and precision SQL data types

Hello Sergei! The proposal makes a lot of sense, and Martijn is right as well. Are you willing to drive the FLIP effort? Do you need any assistance with that? On Mar 4, 2024 at 01:48 +0100, Martijn Visser , wrote: > Hi, > > I think it would first require a FLIP, given it touches on the core type >

[DISCUSS] FLIP-425: Asynchronous Execution Model

Hi devs, I'd like to start a discussion on FLIP-425: Asynchronous Execution Model[1], which is a sub-FLIP of FLIP-423: Disaggregated State Storage and Management[2]. FLIP-425 introduces a non-blocking execution model leveraging the asynchronous APIs introduced in FLIP-424[3]. For the whole story

Re: [DISCUSS] FLIP-433: State Access on DataStream API V2

Hi Zakelly, Thanks for your reply! > My advice would be to conceal RedistributionMode/Strategy from the standard user interface, particularly within the helper class 'State'. But I'm OK to keep it in `StateDeclaration` since its interfaces are basically used by the framework. I'm sorry, I didn't

[DISCUSS] FLIP-428: Fault Tolerance/Rescale Integration for Disaggregated State

Hi devs, I'd like to start a discussion on a sub-FLIP of FLIP-423: Disaggregated State Storage and Management[1], which is a joint work of Yuan Mei, Zakelly Lan, Jinzhong Li, Hangxiang Yu, Yanfei Lei and Feng Wang: - FLIP-428: Fault Tolerance/Rescale Integration for Disaggregated State

[DISCUSS] FLIP-426: Grouping Remote State Access

Hi devs, I'd like to start a discussion on a sub-FLIP of FLIP-423: Disaggregated State Storage and Management[1], which is a joint work of Yuan Mei, Zakelly Lan, Jinzhong Li, Hangxiang Yu, Yanfei Lei and Feng Wang: - FLIP-426: Grouping Remote State Access

[DISCUSS] FLIP-424: Asynchronous State APIs

Hi devs, I'd like to start a discussion on a sub-FLIP of FLIP-423: Disaggregated State Storage and Management[1], which is a joint work of Yuan Mei, Zakelly Lan, Jinzhong Li, Hangxiang Yu, Yanfei Lei and Feng Wang: - FLIP-424: Asynchronous State APIs [2] This FLIP introduces new APIs for asynch

Re: [DISCUSS] FLIP-433: State Access on DataStream API V2

Hi Gyula, Thanks for your reply! Let me answer these questions: > What is the semantics of the usesStates method? When is it called? Can the used state change dynamically at runtime? Can the logic depend on something computed in open(..) for example? useStates is used to predefine all the s