Re: Proposal to improve the Apache Flink website

Hi Deepthi, Thanks for the feedback. Zeplin I mentioned is a UX/UI design software[1], it is not Zeppelin. It is great to hear that Amazon UX/UI designers would contribute. There was a lack of front-end engineers in the past. Hopefully we could find enough front-end contributors for this big

Re: Proposal to improve the Apache Flink website

Hi Deepthi, Welcome to the Flink community. Thanks for the proposal. Commonly speaking, anything that could make Flink more attractive is welcome. I was wondering what your FLIP will look like. Are you going to propose a modern UX/UI design via e.g. Zeplin which could be turned into a technical

Re: [ANNOUNCE] New Apache Flink Committer - Rui Fan

Congrats Rui! On Mon, Feb 20, 2023 at 3:19 PM Piotr Nowojski wrote: > Hi, everyone > > On behalf of the PMC, I'm very happy to announce Rui Fan as a new Flink > Committer. > > Rui Fan has been active on a small scale since August 2019, and ramped up > his contributions in the 2nd half of 2021.

Re: [ANNOUNCE] New Apache Flink Committer - Anton Kalashnikov

Congrats Anton! On Mon, Feb 20, 2023 at 5:02 PM Samrat Deb wrote: > congratulations Anton! > > Bests, > Samrat > > On Mon, 20 Feb 2023 at 9:29 PM, John Roesler wrote: > > > Congratulations, Anton! > > -John > > > > On Mon, Feb 20, 2023, at 08:18, Piotr Nowojski wrote: > > > Hi, everyone > > >

Re: Proposal to add support for Kafka Headers to KafkaRecordSerializationSchemaWrapper

Hi Alex, Just assigned the ticket to you. Kafka Header should be supported as we started implementing the KafkaSink. Thanks for driving this! Best regards, Jing On Fri, Feb 17, 2023 at 3:35 PM Alex Gout wrote: > Hey :) > I created a JIRA for

Re: [DISCUSS] Flink minor version support policy for old releases

+1 Thanks Danny for starting the discussion! This proposal makes a lot of sense. Given that the Flink development is so active, there should be always some bugs fix with the previous minor version waiting to be "flushed" during the time when a new minor version after the current minor version is

Re: [ANNOUNCE] New Apache Flink Committer - Jing Ge

;> On Thu, Feb 16, 2023 at 2:03 PM Dian Fu >> > wrote: >> > > >>> >> > > >>>> Congratulations Jing! >> > > >>>> >> > > >>>> Regards, >> > > >>>> Dian >> > > >&

[jira] [Created] (FLINK-31121) KafkaSink should be able to catch and ignore exp via config on/off

Jing Ge created FLINK-31121: --- Summary: KafkaSink should be able to catch and ignore exp via config on/off Key: FLINK-31121 URL: https://issues.apache.org/jira/browse/FLINK-31121 Project: Flink

Re: [ANNOUNCE] New Apache Flink PMC Member - Dong Lin

Congrats, Dong! On Thu, Feb 16, 2023 at 8:49 AM Martijn Visser wrote: > Congratulations Dong! > > On Thu, Feb 16, 2023 at 8:47 AM zhouenning > wrote: > > > Congratulations, Dong! Best, Eming > > > > > > 在 2023年2月16日 15:30，Geng Biao 写道： > > > > > > Congrats, Dong! Best, Biao Geng 获取 Outlook for

Re: [DISCUSS] Release Flink 1.15.4

+1 On Wed, Feb 15, 2023 at 4:03 PM Konstantin Knauf wrote: > +1 > > Am Mi., 15. Feb. 2023 um 15:21 Uhr schrieb Maximilian Michels < > m...@apache.org>: > > > +1 > > > > On Wed, Feb 15, 2023 at 12:32 PM Danny Cranmer > > wrote: > > > > > > Hi all, > > > > > > I would like to discuss creating a

Re: [DISCUSS] Promote SinkV2 to @Public and deprecate SinkFunction

, but the new Source API is much more > > > stable > > > > and production-ready than SinkV2. > > > > > > > > Iceberg community raised concerns[1] about the workability and > > stability > > > of > > > > Flink connector APIs. >

Re: [ANNOUNCE] New Apache Flink Committer - Weijie Guo

Congrats Weijie! Best regards, Jing On Mon, Feb 13, 2023 at 9:27 AM Lincoln Lee wrote: > Congratulations, Weijie! > > Best, > Lincoln Lee > > > Martijn Visser 于2023年2月13日周一 16:17写道： > > > Congrats Weijie! > > > > On Mon, Feb 13, 2023 at 7:19 AM Weihua Hu > wrote: > > > > > Congratulations,

Re: [DISCUSS] Promote SinkV2 to @Public and deprecate SinkFunction

Hi, We have the same goal to let users migrate to SinkV2. Just marking those interfaces as deprecated or public won't achieve this goal. Frankly speaking, users will start to migrate not because those interfaces are marked as deprecated. They will do it because there is a workable implementation

[jira] [Created] (FLINK-30862) Config doc generation should keep @deprecated ConfigOption

Jing Ge created FLINK-30862: --- Summary: Config doc generation should keep @deprecated ConfigOption Key: FLINK-30862 URL: https://issues.apache.org/jira/browse/FLINK-30862 Project: Flink Issue Type

Re: [DISCUSS] Incorporate performance regression monitoring into routine process

Hi Yanfei, Thanks for your proposal and effort of driving it. I really like the document on how to deal with the performance regressions. This will coach more developers to be able to work with it. I would suggest that more developers will be aware of the performance regressions during the daily

Re: [RESULT][VOTE] Release 1.16.1, release candidate #1

Hi Martijn, Thanks for driving this! Could you roughly estimate when 1.16.1 could be officially released? Best regards, Jing On Mon, Jan 30, 2023 at 2:19 PM Martijn Visser wrote: > Hi all, > > I'm happy to announce that the release for Flink 1.16.1, release candidate > #1 has been unanimously

Re: [ANNOUNCE] FRocksDB 6.20.3-ververica-2.0 released

Hi Yanfei, Thanks for your effort. Looking forward to checking it. Best regards, Jing On Mon, Jan 30, 2023 at 1:42 PM Yanfei Lei wrote: > It is very happy to announce the release of FRocksDB 6.20.3-ververica-2.0. > > Compiled files for Linux x86, Linux arm, Linux ppc64le, MacOS x86, > MacOS

Re: [Discuss] Conventions on driving FLIPs towards consensus

Thanks all for the valuable information. It is a great step to make the FLIP running more smoothly. I'd like to share two additional suggestions: 1. Veto with care - Voter should present her-/him-self and give a veto with her/his own technical justification. No veto is allowed only based on

Re: [VOTE] Externalize AWS formats to flink-connector-aws

+1 Thanks for driving it! Best regards, Jing On Fri, Jan 27, 2023 at 2:36 PM Danny Cranmer wrote: > Hello Hong, thanks for driving this. > > +1 on the proposal and the voting schema looks good. > > Thanks > > On Thu, Jan 26, 2023 at 5:15 PM Teoh, Hong > wrote: > > > Hi all, > > > > As

Re: [DISCUSS] Externalize AWS formats to flink-connector-aws

Hi, +1, I think, for those formats that are only used by one or few specific connectors, it is a good idea to externalize them. Best regards, Jing On Tue, Jan 24, 2023 at 9:44 AM Ahmed Hamdy wrote: > Hi Hong > +1 for the proposal. Additionally I believe it serves the same value for > the

Re: [DISCUSS] Promote SinkV2 to @Public and deprecate SinkFunction

nkV2 to @public in October of last year :) - I'm still > in favour of making this change sooner rather than later. > > Best regards, > > Martijn > > [1] > https://cwiki.apache.org/confluence/display/FLINK/FLIP-171%3A+Async+Sink > [2] https://issues.apache.org/jira/browse/FLIN

Re: Flink connector sinks

Hi, I would recommend consolidating all those discussions like using Sink over SinkFunction, SinkFunktion deprecation, etc. in [1] to keep everyone on the same page. Martijn has already shared a very good big picture with more details in that thread. Let's continue our discussion there. Thanks!

[jira] [Created] (FLINK-30758) Remove sql-client.display.max-column-width

Jing Ge created FLINK-30758: --- Summary: Remove sql-client.display.max-column-width Key: FLINK-30758 URL: https://issues.apache.org/jira/browse/FLINK-30758 Project: Flink Issue Type: Improvement

Re: [DISCUSS] Promote SinkV2 to @Public and deprecate SinkFunction

Hi, There are some typos in my last email, although hopefully I made myself clear with the context, sorry about that: FLIP-179 -> FLIP-197 FlinkKafkaConsumer -> FlinkKafkaProducer Best regards, Jing On Thu, Jan 19, 2023 at 5:30 AM Jing Ge wrote: > Hi, > > Thanks Marti

Re: [DISCUSS] Promote SinkV2 to @Public and deprecate SinkFunction

> Thus, +1 (binding) for this proposal. > > > > [1] https://issues.apache.org/jira/browse/FLINK-2 > > > > Best > > Yun Tang > > > > > > From: Martijn Visser > > Sent: Wednesday, January 18, 2023

Re: [DISCUSS] FLIP-281 Sink Supports Speculative Execution For Batch Job

17. > > > > By the way, if nobody drives the deprecating thing, I would like to start > > another discussion to talk about it. What do you think? > > > > [1] https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws > > > > Thanks, > > Biao /'bɪ.aʊ/ > > > &g

[RESULT][VOTE] FLIP-279 Unified the max display column width for SqlClient and Table APi in both Streaming and Batch execMode

Hi all, I am happy to announce that FLIP-279 Unified the max display column width for SqlClient and Table APi in both Streaming and Batch execMode [1] has been accepted. There are 3 binding votes and 1 non-binding vote [2]: - Jark Wu (binding) - Shengkai Fang (binding) - Shammon FY (non-binding)

Re: [DISCUSS] FLIP-286: Fix the API stability/scope annotation inconsistency in AbstractStreamOperator

Hi Becket, Speaking of tools, we have ArchUnit integrated in Flink. Extending the defined ArchRules [1] a little bit, you will get the wished scan result. [1]

Re: [DISCUSS] FLIP-287: Extend Sink#InitContext to expose ExecutionConfig and JobID

Hi Joao, Thanks for bringing this up. Exposing internal domain instances depends on your requirements. Technically, it is even possible to expose the RuntimeContext [1] (must be considered very carefully). Since you mentioned that you only need to know if objectReuse is enabled, how about just

Re: [DISCUSS] Enabling dynamic partition discovery by default in Kafka source

+1 for the proposal that makes users' daily work easier and therefore makes Flink more attractive. Best regards, Jing On Fri, Jan 13, 2023 at 11:27 AM Qingsheng Ren wrote: > Thanks everyone for joining the discussion! > > @Martijn: > > > All newly discovered partitions will be consumed from

Re: [VOTE] FLIP-281: Sink Supports Speculative Execution For Batch Job

+ 1(not binding) Best Regards, Jing On Thu, Jan 12, 2023 at 10:01 AM Jing Zhang wrote: > +1 (binding) > > Best, > Jing Zhang > > Lijie Wang 于2023年1月12日周四 16:39写道： > > > +1 (binding) > > > > Best, > > Lijie > > > > Martijn Visser 于2023年1月12日周四 15:56写道： > > > > > +0 (binding) > > > > > > Op di

Re: [DISCUSS] FLIP-281 Sink Supports Speculative Execution For Batch Job

Hi Biao, Thanks for driving this. Like Martijn already pointed out. We will spend effort to remove SinkFunction after we deprecate it. The more functionality added into it, the bigger effort we will have to deprecate and remove the SinkFunction. Commonly, It is not recommended to add new features

Re: [DISCUSS] Release Flink 1.16.1

Hi Martijn, +1 and thanks for bringing this up. Since all blocking issues have been resolved afaik, when will the release process be kicked off? Do you have the estimated release date? Best regards, Jing On Thu, Jan 5, 2023 at 3:36 AM Dong Lin wrote: > Hi Martijn, > > Thank you for bringing

Re: [ANNOUNCE] New Apache Flink Committer - Lincoln Lee

congrats! Best regards Jing On Tue, Jan 10, 2023 at 9:39 AM Ryan Skraba wrote: > Congratulations Lincoln! > > All my best, Ryan > > On Tue, Jan 10, 2023 at 9:37 AM yh z wrote: > > > Congratulations, Lincoln! > > > > Best regards, > > Yunhong Zheng > > > > Biao Liu 于2023年1月10日周二 15:02写道： > >

[VOTE] FLIP-279 Unified the max display column width for SqlClient and Table APi in both Streaming and Batch execMode

Hi, I'd like to start a vote on FLIP-279 Unified the max display column width for SqlClient and Table APi in both Streaming and Batch execMode. The discussion can be found at [1]. The vote will last for at least 72 hours (Jan 12th at 9:00 GMT) unless there is an objection or insufficient votes.

Re: [DISCUSS] FLIP-279 Unified the max display column width for SqlClient and Table APi in both Streaming and Batch execMode

Hi Shammon, Thanks for the feedback. Yes, it will work just like you wished. :) Best regards, Jing On Mon, Jan 9, 2023 at 6:31 AM Shammon FY wrote: > Hi @Jing Ge > > Thanks for the proposal and sorry for joining the discussion late. I met > the same problem when I performed a

Re: [DISCUSS] FLIP-279 Unified the max display column width for SqlClient and Table APi in both Streaming and Batch execMode

Hi Dev, I let the discussion open for a longer time because of the holiday session. It seems there are no concerns about this proposal. I will start a voting thread. Thanks! Best regards, Jing On Fri, Dec 16, 2022 at 11:09 AM Jing Ge wrote: > Hi Dev, > > I'd like to start a discuss

[DISCUSS] FLIP-279 Unified the max display column width for SqlClient and Table APi in both Streaming and Batch execMode

Hi Dev, I'd like to start a discussion about FLIP-279: Unified the max display column width for SqlClient and Table APi in both Streaming and Batch execMode[1]. On one side, currently, there is only one ConfigOption SqlClientOptions.DISPLAY_MAX_COLUMN_WIDTH(sql-client.display.max-column-width')

Re: [VOTE] FLIP-273: Improve Catalog API to Support ALTER TABLE syntax

+1(no-binding) On Mon, Dec 5, 2022 at 3:29 PM Zheng Yu Chen wrote: > +1(no-binding) > > Jark Wu 于2022年12月5日周一 11:00写道： > > > +1 (binding) > > > > Best, > > Jark > > > > On Fri, 2 Dec 2022 at 10:11, Paul Lam wrote: > > > > > +1 (non-binding) > > > > > > Best, > > > Paul Lam > > > > > > >

Re: [ANNOUNCE] New Apache Flink PMC Members - Godfrey He, Xingbo Huang

Congrats, Godfrey! Congrats, Xingbo! Best regards, Jing On Wed, Nov 23, 2022 at 6:11 PM Maximilian Michels wrote: > Welcome aboard Godfrey and Xingbo! > > -Max > > On Wed, Nov 23, 2022 at 5:51 PM Yun Tang wrote: > > > Congratulations, Godfrey and Xingbo! > > > > Best > > Yun Tang > >

Re: [ANNOUNCE] New Apache Flink Committer - Matyas Orhidi

Congrats Matyas! Best Regards, Jing On Mon, Nov 21, 2022 at 3:43 PM Ferenc Csaky wrote: > Congrats Matyas! > > Best, > F > > > > --- Original Message --- > On Monday, November 21st, 2022 at 15:17, Márton Balassi < > mbala...@apache.org> wrote: > > > > > > > > Hi everyone, > > > > On

Re: [Vote] Remove FlinkKafkaConsumer and graduate related Source APIs

ing, > > I realized that there is a missing feature with KafkaSource that might > prevent existing users of FlinkKafkaConsumer from migrating to > FlinkKafkaConsumer. > I have put more details in the discussion thread. > > Thanks, > Dong > > > On Wed, Nov 16, 2022 at

Re: [DISCUSS] Remove FlinkKafkaConsumer and FlinkKafkaProducer in the master for 1.17 release

ore alternative solutions. > My priority changed recently and don't plan to get this FLIP done for 1.17. > It will be great if someone can address this issue so that we can move > forward to remove FlinkKafkaConsumer. > > Thanks, > Dong > > > > > > O

[Vote] Remove FlinkKafkaConsumer and graduate related Source APIs

Hi, As discussed on the mailing list[1]. I'd like to start a vote to remove FlinkKafkaConsumer and graduate related Source APIs. Since there are some ongoing developments which will change SinkV2 APIs, depending on how far it would go, I might start another vote to remove FlinkKafkaProducer

[jira] [Created] (FLINK-30025) table.execute().print() can only use the default max column width

Jing Ge created FLINK-30025: --- Summary: table.execute().print() can only use the default max column width Key: FLINK-30025 URL: https://issues.apache.org/jira/browse/FLINK-30025 Project: Flink

Re: [DISCUSS] Remove FlinkKafkaConsumer and FlinkKafkaProducer in the master for 1.17 release

@David > > > About the ability of DeserializationSchema#isEndOfStream, FLIP-208 is > > > trying to complete this piece of the puzzle, and Hang Ruan ( > > > ruanhang1...@gmail.com) plans to work on it in 1.17. For the partition > > > idleness problem could you elabo

[jira] [Created] (FLINK-29999) Improve documentation on how a user should migrate from FlinkKafkaConsumer to KafkaSource

Jing Ge created FLINK-2: --- Summary: Improve documentation on how a user should migrate from FlinkKafkaConsumer to KafkaSource Key: FLINK-2 URL: https://issues.apache.org/jira/browse/FLINK-2

Re: [blog article] Howto migrate a real-life batch pipeline from the DataSet API to the DataStream API

Hi Etienne, Nice blog! Thanks for sharing! Best regards, Jing On Wed, Nov 9, 2022 at 5:49 PM Etienne Chauchot wrote: > Hi Yun Gao, > > FYI I just updated the article after your review: > https://echauchot.blogspot.com/2022/11/flink-howto-migrate-real-life-batch.html > > Best > > Etienne > Le

Re: [ANNOUNCE] Performance Daily Monitoring Moved from Ververica to Apache Flink Slack Channel

Thanks yanfei for driving this! Looking forward to further discussion w.r.t. the workflow. Best regards, Jing On Mon, Oct 31, 2022 at 6:04 PM Mason Chen wrote: > +1, thanks for driving this! > > On a side note, can we also ensure that a performance summary report for > Flink major version

Re: [DISCUSS] Flink release retro

Hi all, I figure it is a good idea and +1 for the async retro. More developers will learn from what the release process looks like, which will give them context to engage in future releases. It would be great if the conversation could somehow follow the traditional retro pattern, e.g. tagged with

Re: [DISCUSS] Remove FlinkKafkaConsumer and FlinkKafkaProducer in the master for 1.17 release

ps://www.mail-archive.com/user@flink.apache.org/msg44618.html > > > [2] https://www.mail-archive.com/user@flink.apache.org/msg45864.html > > > > > > On Mon, Oct 31, 2022 at 7:32 PM Piotr Nowojski > > > wrote: > > > > > > > Hi, > > > &

Re: [ANNOUNCE] New Apache Flink PMC Member - Danny Cranmer

Congrats, Danny! Best regards, Jing On Tue, Nov 1, 2022 at 11:42 AM Hamdy, Ahmed wrote: > Congratulations, Danny! > Best, > Ahmed > > On 01/11/2022, 09:51, "Yuxin Tan" wrote: > > CAUTION: This email originated from outside of the organization. Do > not click links or open attachments

Re: [DISCUSS] Remove FlinkKafkaConsumer and FlinkKafkaProducer in the master for 1.17 release

1.15). > > Thanks, > > Martijn > > On Thu, Oct 27, 2022 at 2:06 PM Jing Ge wrote: > > > Hi Dev, > > > > I'd like to start a discussion about removing FlinkKafkaConsumer and > > FlinkKafkaProducer in 1.17. > > > > Back in the past,

Re: [VOTE] Dedicated AWS externalized connector repo

+1 (non-binding) Thanks! Best Regards, Jing On Fri, Oct 28, 2022 at 5:29 PM Samrat Deb wrote: > +1 (non binding) > > Thanks for driving Danny > > Bests > Samrat > > On Fri, 28 Oct 2022 at 8:36 PM, Ahmed Hamdy wrote: > > > +1 (non-binding) > > Regards, > > Ahmed > > > > On Thu, 27 Oct 2022 at

Re: [ANNOUNCE] Apache Flink 1.16.0 released

Congrats! On Fri, Oct 28, 2022 at 1:22 PM 任庆盛 wrote: > Congratulations and a big thanks to Chesnay, Martijn, Godfrey and Xingbo > for the awesome work for 1.16! > > Best regards, > Qingsheng Ren > > > On Oct 28, 2022, at 14:46, Xingbo Huang wrote: > > > > The Apache Flink community is very

[DISCUSS] Remove FlinkKafkaConsumer and FlinkKafkaProducer in the master for 1.17 release

Hi Dev, I'd like to start a discussion about removing FlinkKafkaConsumer and FlinkKafkaProducer in 1.17. Back in the past, it was originally announced to remove it with Flink 1.15 after Flink 1.14 had been released[1]. And then postponed to the next 1.15 release which meant to remove it with

Re: [DISCUSS] Release Flink 1.15.3

+1 The timing is good to have 1.15.3 release. Thanks Fabian for bringing this to our attention. I just checked PRs and didn't find the 1.15 backport of FLINK-29567 . Please be aware of it. Thanks! Best regards, Jing On Tue, Oct 25, 2022 at

Re: [Cassandra] source connector

Hi, The plan was and the ideal process is to try the externalizing connector development and release with the elastic connector first and make it stable before starting the migration of other connectors. There are already many connectors like Iceberg and AWS connectors that are trying

Re: [DISCUSS] REST API to suspend & resume checkpointing

act > > > > > issue. Which brings me to... > > > > > 3. You could actually just use the REST API to trigger all > > checkpoints > > > > > manually. The idea behind FLINK-27101 [1] was to add full > flexibility > > &

Re: [DISCUSS] Create a dedicated aws-base connector repository

I agree with Jark. It would be easier for the further development and maintenance, if all aws related connectors and the base module are in the same repo. It might make sense to upgrade the flink-connector-dynamodb to flink-connector-aws and move the other modules including the

Re: [DISCUSS] Planning Flink 1.17

+1 The plan looks rational. Thanks for your effort! Best regards, Jing On Fri, Oct 21, 2022 at 1:16 PM Congxian Qiu wrote: > Thanks for kicking off the 1.17 release, and volunteers as release > managers. > > +1 to the feature freeze date > > Best, > Congxian > > > Yun Tang 于2022年10月21日周五

Re: [Discuss]- Donate Iceberg Flink Connector

I agree with Steven Wu that those points are applicable to every externalized connector. So those were actually concerns about externalizing connector development and there were already some discussions and consensus has already been made to do it. Speaking of the 3x3 concern, I think the

Re: [DISCUSS] REST API to suspend & resume checkpointing

Hi Saurabh, In general, it is always good to add new features. I am not really sure if I understood your requirement. I guess it will be too long for you to resume the job with a created savepoint in the new stand-by Flink cluster. But if it would be acceptable to you, you should not have the

Re: [VOTE] FLIP-265 Deprecate and remove Scala API support

+1 On Wed, Oct 19, 2022 at 10:31 AM David Anderson wrote: > +1 > > > > On Mon, Oct 17, 2022 at 3:39 PM Martijn Visser > wrote: > > > Hi everyone, > > > > I'm hereby opening a vote for FLIP-265 Deprecate and remove Scala API > > support. The related discussion can be found here [1]. > > > >

Re: [VOTE] Drop Gelly

+1 and I second Yu Li and Yun Gao. It should be also pointed out that Flink will continue to support graph processing with a new plan in the upcoming 1.17 release notes which includes the change of dropping Gelly in order to let more developers and users be aware of it. Best regards, Jing On

Re: [VOTE] Externalized connector release details​

> > Here 4.1.b kicks in, ensuring that v2 is still supported since we need > > to support all Flink versions. > > > > > > Now 1.18 is released, with v3 and v4 supporting it. > > > > v2: 1.15-1.17 (no support) > > v3: 1.17 (patch support) > > v4: 1.17

Re: [VOTE] Reverting sink metric name changes made in 1.15

+1 The voting title might cause confusion. Technically to say, it is a further modification on top of the current status rather than a reverting after considering the backward compatibility. Best regards, Jing On Fri, Oct 14, 2022 at 10:41 AM Qingsheng Ren wrote: > Thanks for the reply

Re: [DISCUSS] Reverting sink metric name changes made in 1.15

e IO. This needs time to design, discuss, adjust > and vote, but considering this is blocking 1.16, maybe it’s better to > rescue the compatibility for now, and leave the huge reconstruction to > future versions (maybe 2.0). > > Best, > Qingsheng > > On Wed, Oct 12, 2022 a

Re: [VOTE] Externalized connector release details​

+1 and I would suggest giving a concrete example to explain 4) support. It is still not quite easy to understand the text. Not many (future) connector developers could join this discussion. It is better to make it as clear as possible at the beginning than spend more time explaining multiple

Re: [DISCUSS] Reference operator from Flink Kubernetes deployment docs

+1 good idea! On Thu, Oct 13, 2022 at 2:42 PM Yang Wang wrote: > +1 for increasing the visibility of flink-kubernetes-operator. > > Best, > Yang > > Thomas Weise 于2022年10月13日周四 07:49写道： > > > +1 > > > > > > On Wed, Oct 12, 2022 at 5:03 PM Martijn Visser > > > wrote: > > > > > +1 from my end

Re: [DISCUSS] Reverting sink metric name changes made in 1.15

Hi Qingsheng, Just want to make sure we are on the same page. Are you suggesting switching the naming between "numXXXSend" and "numXXXOut" or reverting all the changes we did with FLINK-26126 and FLINK-26492? For the naming switch, please pay attention that the behaviour has been changed since

Re: [DISCUSS] FLIP-265 Deprecate and remove Scala API support

Hi Martijn, Thanks for bringing this up. It is generally a great idea, so +1. Since both scala extension projects mentioned in the FLIP are still very young and I don't think they will attract more scala developers as Flink could just because they are external projects. It will be a big issue

Re: [DISCUSS] FLIP-264 Extract BaseCoordinatorContext

Thanks for bringing this up. It looks overall good! One small thing, you might want to write all content on the wiki page instead of linking to a google doc. The reason is that some people might not be able to access the google doc. Best regards, Jing On Tue, Oct 4, 2022 at 3:57 AM gang ye

Re: [VOTE] Release 1.14.6, release candidate #2

+1 (not binding) - checkout the source code with the tag. - source archives do not contain any binaries. - built the source code with maven. - started a session cluster and ran WordCount in both streaming and batch mode. Best regards, Jing On Mon, Sep 26, 2022 at 9:30 AM Yun Gao wrote: > +1

Re: [DISCUSS] Externalized connector release details

Hi, Thanks for starting this discussion. It is an interesting one and yeah, it is a tough topic. It seems like a centralized release version schema control for decentralized connector development ;-) In general, I like this idea, not because it is a good one but because there might be no better

[jira] [Created] (FLINK-29289) SequencefileInputFormat based on the new Source API

Jing Ge created FLINK-29289: --- Summary: SequencefileInputFormat based on the new Source API Key: FLINK-29289 URL: https://issues.apache.org/jira/browse/FLINK-29289 Project: Flink Issue Type: New

Re: [ANNOUNCE] New Apache Flink PMC Member - Martijn Visser

Congrats! On Mon, Sep 12, 2022 at 9:38 AM Daisy Tsang wrote: > Congrats! > > On Mon, Sep 12, 2022 at 9:32 AM Martijn Visser > wrote: > > > Thank you all :) > > > > Op zo 11 sep. 2022 om 13:58 schreef Zheng Yu Chen : > > > > > Congratulations, Martijn > > > > > > > > > > > > Timo Walther

Re: [ANNOUNCE] New Apache Flink Committer - Caizhi Weng

Congrats Chaizhi! Best regards, Jing On Fri, Sep 9, 2022 at 7:23 AM Benchao Li wrote: > Congratulations Caizhi! > > Jark Wu 于2022年9月9日周五 11:46写道： > > > Congrats ChaiZhi! > > > > Cheers, > > Jark > > > > > 2022年9月9日 11:26，Lijie Wang 写道： > > > > > > Congratulations Caizhi > > > > > > Best, > >

[jira] [Created] (FLINK-29224) flink-mirror does not pick up the new release branch 1.16

Jing Ge created FLINK-29224: --- Summary: flink-mirror does not pick up the new release branch 1.16 Key: FLINK-29224 URL: https://issues.apache.org/jira/browse/FLINK-29224 Project: Flink Issue Type

Re: [ANNOUNCE] Apache Flink 1.15.2 released

Thanks Danny for your effort! Best regards, Jing On Wed, Aug 24, 2022 at 11:43 PM Danny Cranmer wrote: > The Apache Flink community is very happy to announce the release of Apache > Flink 1.15.2, which is the second bugfix release for the Apache Flink 1.15 > series. > > Apache Flink® is an

[jira] [Created] (FLINK-29095) logging state file deletion

Jing Ge created FLINK-29095: --- Summary: logging state file deletion Key: FLINK-29095 URL: https://issues.apache.org/jira/browse/FLINK-29095 Project: Flink Issue Type: New Feature

Re: [DISCUSS] FLIP-256 Support Job Dynamic Parameter With Flink Rest Api

+1 for the FLIP. I like this FLIP. It is very useful. I'd like to ask one more question: " - The internal parameters passed in by the user contains the external parameter. At this point, we can see that the user configures the same two parameters in the *external parameter* and

Re: [ANNOUNCE] New Apache Flink Committer - Lijie Wang

Congrats Lijie! Best regards, Jing On Thu, Aug 18, 2022 at 8:40 AM Terry Wang wrote: > Congratulations, Lijie! > > On Thu, Aug 18, 2022 at 11:31 AM Leonard Xu wrote: > > > Congratulations, Lijie! > > > > Best, > > Leonard > > > > > 2022年8月18日 上午11:26，Zhipeng Zhang 写道： > > > > > >

Re: [ANNOUNCE] New Apache Flink Committer - Junhan Yang

Congrats Junhan! Best regards, Jing On Thu, Aug 18, 2022 at 12:05 PM Jark Wu wrote: > Congrats and welcome Junhan! > > Cheers, > Jark > > > 2022年8月18日 17:59，Timo Walther 写道： > > > > Congratulations and welcome to the committer team :-) > > > > Regards, > > Timo > > > > On 18.08.22 07:19,

[jira] [Created] (FLINK-29003) sqlServerDialect should support limit clause

Jing Ge created FLINK-29003: --- Summary: sqlServerDialect should support limit clause Key: FLINK-29003 URL: https://issues.apache.org/jira/browse/FLINK-29003 Project: Flink Issue Type: New Feature

Re: [DISCUSS] Releasing Flink 1.15.2

Thanks Danny! Strong +1 and looking forward to the 1.15.2 asap. Best regards, Jing On Fri, Aug 12, 2022 at 4:25 AM Xingbo Huang wrote: > Hi Danny, > > Thanks for driving the release. +1 for the 1.15.2 release. > > Best, > Xingbo > > Chesnay Schepler 于2022年8月11日周四 20:06写道： > > > I think that's

[jira] [Created] (FLINK-28778) Bulk fetch of table and column statistics for given partitions

Jing Ge created FLINK-28778: --- Summary: Bulk fetch of table and column statistics for given partitions Key: FLINK-28778 URL: https://issues.apache.org/jira/browse/FLINK-28778 Project: Flink Issue

[RESULT][VOTE] FLIP--247 Bulk fetch of table and column statistics for given partitions

Hi, everyone. FLIP--247 Bulk fetch of table and column statistics for given partitions[1] has been accepted. There are 3 binding votes, 1 non-binding votes[2]. - Jark Wu(binding) - Godfrey He(binding) - Jingsong Li(binding) - Rui Fan(non-binding) None against. Thanks everyone! Best regards,

Re: I want to contribute to Apache Flink.

Hi, Do you mean you want to have the access rights to the FLIP wiki page[1]? Your confluence ID is required in this case, which is different from the Jira ID. Generally, you don't need any specific permissions to do contributions. Please follow the introduction [1] and then find some jira issues

Re: [VOTE] FLIP-248: Introduce dynamic partition pruning

+1 Thanks for driving this! On Tue, Jul 26, 2022 at 4:01 PM godfrey he wrote: > Hi everyone, > > Thanks for all the feedback so far. Based on the discussion[1] we seem > to have consensus, so I would like to start a vote on FLIP-248 for > which the FLIP has now also been updated[2]. > > The

[VOTE] FLIP-247 Bulk fetch of table and column statistics for given partitions

Hi all, Many thanks for all your feedback. Based on the discussion in [1], I'd like to start a vote on FLIP-247 [2]. The vote will last for at least 72 hours unless there is an objection or insufficient votes. Best regards, Jing [1]

Re: [DISCUSS] FLIP-247 Bulk fetch of table and column statistics for given partitions

Hi, I have updated the FLIP. Please check again. If there are no other concerns, I will start voting. Thank you all for your support! Best regards, Jing On Fri, Jul 22, 2022 at 1:32 PM Jing Ge wrote: > Thanks Jark, fair enough, I will update the FLIP accordingly. > > Best regard

Re: [DISCUSS] FLIP-247 Bulk fetch of table and column statistics for given partitions

whether > the Catalog implements the bulk method or not. > This can also address the above concerns. > > What do you think? > > Best, > Jark > > > > > > On Thu, 21 Jul 2022 at 21:13, Jing Ge wrote: > > > Thanks Jingsong and Jark. I will create another FLIP t

Re: [DISCUSS] FLIP-247 Bulk fetch of table and column statistics for given partitions

HiveMetastoreClient.listPartitions. But on our side, we > > need Catalog.getPartitions first, and then > > Catalog.bulkGetPartitionStatistics. > > > > - Consider bulkGetPartitionColumnStatistics, yes, as you said, we need > it. > > > > But to unify them, the current FLIP is accept

Re: [DISCUSS] FLIP-248: Introduce dynamic partition pruning

Hi, Thanks for the informative discussion! Looking forward to using dynamic filtering provided by Flink. Best regards, Jing On Tue, Jul 19, 2022 at 3:22 AM godfrey he wrote: > Hi, Jingong, Jark, Jing, > > Thanks for for the important inputs. > Lake storage is a very important scenario, and

Re: [DISCUSS] FLIP-247 Bulk fetch of table and column statistics for given partitions

tistics returned by a new method called `listPartitionWithStats`? > Best, > Jingsong > > On Tue, Jul 19, 2022 at 8:44 PM Jing Ge wrote: > > > > Thanks Jingsong for the suggestion. > > > > Do you mean using a different naming convention? There is a thought and &

Re: [VOTE] FLIP-238: Introduce FLIP-27-based Data Generator Source

+1(non-binding) Thanks for driving this! Best regards, Jing On Wed, Jul 20, 2022 at 7:48 AM Robert Metzger wrote: > +1 > > On Wed, Jul 20, 2022 at 4:41 AM Rui Fan <1996fan...@gmail.com> wrote: > > > +1(non-binding) > > > > New Source can better support some features, such as > > Unaligned

Re: [DISCUSS] FLIP-247 Bulk fetch of table and column statistics for given partitions

t; > for the optimizer. > > The FLIP looks good to me. > > > > Best, > > Jark > > > > On Fri, 8 Jul 2022 at 17:36, Jing Ge wrote: > > > > > Hi devs, > > > > > > After having multiple discussions with Jark and Goldfrey, I'

[DISCUSS] FLIP-247 Bulk fetch of table and column statistics for given partitions

Hi devs, After having multiple discussions with Jark and Goldfrey, I'd like to start a discussion on the mailing list w.r.t. FLIP-247[1], which will significantly improve the performance by providing the bulk fetch capability for table and column statistics. Currently the statistics information

Re: [DISCUSS] Creating benchmark channel in Apache Flink slack

+1 for moving to the public slack channel. Flink developers should pay more attention to the performance test. Best regards, Jing On Thu, Jul 7, 2022 at 2:02 PM Yuan Mei wrote: > +1 for the proposal Anton, and thanks very much to move this effort > forward! > > In long term, I think it would

<    1   2   3   4   5   6   7   8   >