[jira] [Created] (FLINK-38144) Change log state backend is not compatible with the case where the user value of the map state is null

Rui Fan created FLINK-38144: --- Summary: Change log state backend is not compatible with the case where the user value of the map state is null Key: FLINK-38144 URL: https://issues.apache.org/jira/browse/FLINK-38144

Re: Re: [DISCUSS] FLIP-535:Introduce RateLimiter to Source

Hi, Zexian. Thanks for your FLIP. I think rate litmit is very important feature for our users. But I have some questions about the FLIP: 1. How do I determine the input parameter `requestSize` for `RateLimiter#acquire`? If the rate limiter indicates there are 2 remaining requests that can be emit

Re: [VOTE] Release 2.1.0, release candidate #1

Thanks all for the voting. I'll close the vote in a separate thread. Best, Ron Leonard Xu 于2025年7月28日周一 11:27写道： > +1 (binding) > > - verified signatures > - verified hashsums > - checked Github release tag > - checked release notes > - ran SQL values test via SQL client in standalone cluster >

[DISCUSS] FLIP-538: Support Custom Generic Type Serializer

Hi everyone, I'd like to start a discussion of FLIP-538: Support Custom Generic Type Serializer [1]. Flink handles most common types efficiently with the built-in serializers and leaves the remaining to the generic type serializer Kryo in a hardcoded way. We propose supporting custom generic t

Re: [VOTE] Release 2.1.0, release candidate #1

+1 (non-binding) Checklist: - verified tarball checksums & gpg signatures are valid - built from source successfully on macOS with JDK 17 and Maven 3.8.x - started a local standalone cluster and verified the Web UI and logs - ran simple queries via the sql-client in batch mode - confirmed the git

RE: Re: [DISCUSS] FLIP-535:Introduce RateLimiter to Source

Hi Leonard, Thanks a lot for your support and positive feedback! I'm glad to hear you think the design meets the needs of most scenarios. Indeed, rate limiting is a fundamental and important feature, and I'm excited to help fill this gap. I'm also looking forward to more ideas and potential impro

Re: [VOTE] Release 2.1.0, release candidate #1

+1 (non-binding) Checklist: - verified tarball checksums & gpg signatures are valid - built from source successfully on macOS with JDK 17 and Maven 3.8.x - started a local standalone cluster and verified the Web UI and logs - ran simple queries via the sql-client in batch mode - confirmed the git

Re: [VOTE] Release 2.1.0, release candidate #1

+1 (non-binding) Checklist: - verified tarball checksums & gpg signatures are valid - built from source successfully on macOS with JDK 17 and Maven 3.8.x - confirmed the git release tag `release-2.1.0-rc1` is correct Best Regards, Zexian > 2025年7月21日 21:40，Ron Liu 写道： > > Hi everyone, >

RE: Re: [DISCUSS] FLIP-535:Introduce RateLimiter to Source

Hi Leonard, Thanks a lot for your support and positive feedback! I'm glad to hear you think the design meets the needs of most scenarios. Indeed, rate limiting is a fundamental and important feature, and I'm excited to help fill this gap. I'm also looking forward to more ideas and potential im

Re: [VOTE] Release 2.1.0, release candidate #1

+1 (no binding) - verified & checksums - use release-2.1.0-rc1.tar.gz to run sql jobs. Best, Hongshun On Mon, Jul 28, 2025 at 11:27 AM Leonard Xu wrote: > +1 (binding) > > - verified signatures > - verified hashsums > - checked Github release tag > - checked release notes > - ran SQL values te

Re: [VOTE] Release 2.1.0, release candidate #1

+1 (binding) - verified signatures - verified hashsums - checked Github release tag - checked release notes - ran SQL values test via SQL client in standalone cluster - checked compiled version 55.0 (Java SE 11) - reviewed the web PR, left two comments 'NEED' to fix Best, Leonard > On 2025 Jul

Re: [DISCUSS] FLIP-529 Connections in Flink SQL and Table API

Hi Yanquan, Thanks for the feedback. > (1) I agree with the design of SecretStore. I hope to add the results of the 'SHOW Connections' query to the document, 'secret.id' should be included in the results, This helps us establish the association between tables and connections. I think we can outp

Re: [VOTE] Release 2.1.0, release candidate #1

Hi Ron, When reading the jira release notes, I found there might be some tickets that are not fixed in 2.1.0 (still open) but labeled 2.1.0, e.g. FLINK-9879[1] and FLINK-10113[2]. Correct me if I'm wrong. Shall we revisit those open tickets which are labeled 2.1.0 and see if they are actually done

Re: [VOTE] Release 2.1.0, release candidate #1

Hi, Zakelly These open issues will be moved to version 2.2.0 after release, which will require a PMC member to help with this. Best, Ron Zakelly Lan 于2025年7月28日周一 14:00写道： > Hi Ron, > > When reading the jira release notes, I found there might be some tickets > that are not fixed in 2.1.0 (stil

Re: [DISCUSS] FLIP-529 Connections in Flink SQL and Table API

Hi Mayank and Hao, Thanks for the updates and comments. Here are some of my opinions: (1) I agree with the design of SecretStore. I hope to add the results of the 'SHOW Connections' query to the document, 'secret.id' should be included in the results, This helps us establish the association betwee