[jira] [Created] (FLINK-37751) Add vertex name to autoscaler metrics

Sai Sharath Dandi created FLINK-37751: - Summary: Add vertex name to autoscaler metrics Key: FLINK-37751 URL: https://issues.apache.org/jira/browse/FLINK-37751 Project: Flink Issue Type: I

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

Hi all, I would like to open up for discussion a new FLIP-529 [1]. Motivation: Currently, Flink SQL handles external connectivity by defining endpoints and credentials in table configuration. This approach prevents reusability of these connections and makes table definition less secure by exposin

Re: KinesisStreamSource de-aggregation support via DeserializationSchema

Hi Lorenzo, I am not sure I follow the issue of awaiting a major release, we have seen the major releases for AWS connectors being picked up quite fast so we can just push for one. Plus the contribution is not a bug fix, additionally the legacy source is not yet removed. hence I would personally no

[jira] [Created] (FLINK-37750) Remove legacy function runIfNotDoneAndGet() in FutureUtils class

Pranav Mahajan created FLINK-37750: -- Summary: Remove legacy function runIfNotDoneAndGet() in FutureUtils class Key: FLINK-37750 URL: https://issues.apache.org/jira/browse/FLINK-37750 Project: Flink

[VOTE] Apache Flink CDC Release 3.4.0, release candidate #3

Hi everyone, Please review and vote on the release candidate #3 for the version 3.4.0 of Apache Flink CDC, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) *Release Overview* As an overview, the release consists of the following: a) Flink

[jira] [Created] (FLINK-37749) FileSystem Connector fails writing to S3 bucket

Fred Teunissen created FLINK-37749: -- Summary: FileSystem Connector fails writing to S3 bucket Key: FLINK-37749 URL: https://issues.apache.org/jira/browse/FLINK-37749 Project: Flink Issue Typ

RE: Re: [DISCUSS] FLIP-527 Support EXPLAIN EXECUTE STATEMENT SET Syntax in Flink SQL

I agree with Martijn. It’s just a better, consistent user experience. Also, we keep backwards compatibility, so I see no reason for not doing it. I’d also be +1 for this. On 2025/04/29 07:40:59 Martijn Visser wrote: > Hi all, > > Thanks for the FLIP Ramin. I would be +1 for this. It creates a

Re: [DISCUSS] FLIP-520: Simplify StructuredType handling

Hi Hao, thanks for your feedback. Currently, the Python API does not support structured types at all. So this might require another FLIP in the future with a dedicated effort. However, I have considered Python already in the design. Also Python classes are discoverable from a fully qualified

[VOTE] FLIP-518: Introduce a community review process

As below – starting a new vote thread (thanks @Robert Metzger). I'd like to start a vote for FLIP-518: Introduce a community review process [1] which has been discussed in this thread [2]. The vote will be open for at least 72 hours unless there is an objection or not

Re: [VOTE] Apache Flink CDC Release 3.4.0, release candidate #2

FLINK-37104 points out an obvious performance rollback issue, which is indeed a blocker that affects user experience. I will initiate a new release request later after the corresponding PR merge. Leonard Xu 于2025年4月28日周一 16:16写道： > Thanks @Yanquan and @Xiqian for preparing the RC2. > > -1 as FLI

Re: [DISCUSS] FLIP-527 Support EXPLAIN EXECUTE STATEMENT SET Syntax in Flink SQL

Hi all, Thanks for the FLIP Ramin. I would be +1 for this. It creates a consistent experience for SQL users, because they only have to prefix their earlier SQL statement with EXPLAIN in order to get the result. @Ron I don't think it's so much about the efforts that's required to remove the EXECUT