RE: Stale PR Action running but the labels are missing

x27;t have the power to add > > labels to PRs. Is that something that can be granted to me on Github? > > > > Along those lines, it would be useful for those of us in the CHI to be > > able to label PRs with things like "ready-to-merge" (to help committers > &g

FW: Community Health Initiative (CHI) 9th of January minutes

Hi We ran the 7th Community Health Initiative (CHI) on the 16th of January details https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=337678600 The high level summary: * We have identified 10 PRs that should be merged – please could a committer merge these. * We have activa

Re: [DISCUSSION] flink-connector-hive first release of externalized connector

Hi Sergey, I think this makes a lot of sense to get this cleared up soon. I notice that there is a HiveCatalog referred to in the Python in core Flink. I suspect this relates to the HiveCatalog class in core Flink. Do we need to remove the Hive part of Python as part of this , or potentially ch

RE: Stale PR Action running but the labels are missing

Hi Rui, Looks good. I ran: https://github.com/apache/flink/pulls?q=is%3Apr+is%3Aopen+This+PR+is+being+marked+as+stale+since+it+has+not+had+any+activity+in+the+last+180+days. And there are 610 open PRs. I am wondering how we get the stale label onto those PRs. Some thoughts 1. We write batch s

Community Health Initiative (CHI) 9th of January minutes

Hi We ran the 6th Community Health Initiative (CHI) on the 9th of January . Here is the summary * 47 non draft PRs came in since before the holidays, of these * there were a few around migrating table planner

PR introducing V1 and V2 state migration issue

Hi, While reviewing PRs for the Community Health Initiate – I saw https://github.com/apache/flink/pull/25896 The proposal is to upgrade Kyro to remove the Twitter Chill library which is a Scala companion library for Kryo that has been abandoned. This is a great motivation, but will cause an issu

[jira] [Created] (FLINK-37097) Remove

david radley created FLINK-37097: Summary: Remove Key: FLINK-37097 URL: https://issues.apache.org/jira/browse/FLINK-37097 Project: Flink Issue Type: Technical Debt Components

Flink v2 download name

Hi , I notice that the Flink v2 preview download artifact includes scala in the name. https://www.apache.org/dyn/closer.lua/flink/flink-2.0-preview1/flink-2.0-preview1-bin-scala_2.12.tgz As we are removing the Scala API in Flink v2 and also we are looking to replace the table planner Scala implem

RE: Does Flink operator 1.1.0 support Flink 1.20?

.20 in FLINK-36129[1]. [1] https://issues.apache.org/jira/browse/FLINK-36129 Best, Rui On Wed, Jan 8, 2025 at 9:49 PM David Radley wrote: > Hi, > > We were looking at the documentation and wondered is there a statement > saying that the 1.10.0< > https://mvnrepository.com/artifac

Does Flink operator 1.1.0 support Flink 1.20?

Hi, We were looking at the documentation and wondered is there a statement saying that the 1.10.0 Flink operator supports / has been verified with Flink 1.20? Kind regards, David. Unless otherwise st

RE: [VOTE] CHI: Stale PR cleanup

Thanks for driving this Tom. +1 (non-binding) David From: Gyula Fóra Date: Monday, 6 January 2025 at 16:33 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [VOTE] CHI: Stale PR cleanup +1 (binding) Gyula On Mon, Jan 6, 2025 at 5:12 PM Tom Cooper wrote: > Hi all, > > Following on from my propo

Flink technical debt. Chi meeting

triaging and also get bigger changes in place to help, e.g. enhancing Flink bot and a stale PR bot, so we can see what is important to address. Merry Flinkmas !! May all your streams come true 😊 Kind regards ,David, From: David Radley Date: Tuesday, 17 December 2024 at 09:23 To: dev

RE: [VOTE] FLIP-493: Add K8S conditions to CRD's Status

+1 (non-binding) from me Gyula: Yes I agree, let’s leave this open till then. I just wanted to check you are ok with running being the condition we use for both application and session cluster; this is even simpler than your post on the 23rd of September. Running = business as usual = started

FW: FW: Re: Flink technical debt. Chi meeting

v list. * We talked about addressing the dependabot PRs by raising a separate Jira and PR including the notice file(s), so the impact of a dependency upgrade could be properly assessed. Kind regards, David. From: David Radley Date: Thursday, 5 December 2024 at 15:14 To: dev@flink.apac

RE: [DISCUSS] FLIP-XXX Add K8S conditions to Flink CRD

gt; "FlinkSessionJob". >> >> Best, >> Ferenc >> >> >> >> On Wednesday, November 6th, 2024 at 17:33, David Radley < >> david_rad...@uk.ibm.com> wrote: >> >> > >> > >> > Hi lajith, >> > Yes I lik

RE: Re: [DISCUSS] Flink 1.20.1 release

+1 for a 1.20.1 release, Thanks for driving Alex! There is a PR [1] against master that fixes a lot of vulnerabilities in the Web UI, this requires a PR that brings in a later level of Node [2]. We would like to backport these and have them part of the 1.20.1 release, Kind regards, David. [1] h

RE: Plans for JDBC connector for 1.20?

e.org/jira/browse/FLINK-35109. Best Regards Peter Huang On Mon, Dec 9, 2024 at 7:27 PM Hang Ruan wrote: > Hi, Yanquan & David. > > I would like to help to release the version jdbc-3.3.0. > Thanks~ > > Best, > Hang > > On Tue, Dec 3, 2024 at 10:42 PM Dav

RE: [VOTE] FLIP-484: Add custom metric variables to operators

would be good to start with this FLIP Best, Piotrek [1] https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics/#system-scope [2] https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/metric_reporters/#scope-variables-additional [3] https://nightlies.apache.org/flink/f

RE: [VOTE] FLIP-484: Add custom metric variables to operators

Hi, Sorry I am late to this. I have some comments. If I am understanding this correctly, the custom metric is not a new metric that has been customized, it is the ability to add readable useful names / tags as scopes to existing metrics. If this is the case I suggest changing the method name fr

FW: Re: Flink technical debt. Chi meeting

regards, David. From: David Radley Date: Friday, 29 November 2024 at 12:07 To: dev@flink.apache.org , Tom Cooper , Robert Metzger Subject: FW: [EXTERNAL] Re: Flink technical debt. Hi all, We had the 2nd 30 minute working meeting of the Community Health Initiative (CHI) yesterday for Western

RE: Blue/Green Deployments support for Flink

Hi Sergio, +1 for starting a FLIP. I am wondering how non zero values for table.exec.source.idle-timeout and table.exec.state.ttl side effects, as they are based on clock time. It will be interesting to identify these less stable scenarios and see what we can do with them. Kind regards, Davi

RE: Plans for JDBC connector for 1.20?

oject%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%20jdbc-3.3.0 > 2024??11??22?? 01:15??David Radley ?? > > Hi, > Is there a plan to release the JDBC for Flink 1.20? Apologies if this is > already in hand, I cou

Community Health Initiative (CHI) workgroup wiki content

Hi, Thankyou Robert : I now have edit access to the wiki and have added the CHI meeting details here in a new Workgroups section, as suggested by Robert. Each CHI meeting I will add the m

FW: Plans for JDBC connector for 1.20?

Hi again, A friendly nudge – any thoughts from the community? Kind regards, David. From: David Radley Date: Thursday, 21 November 2024 at 17:17 To: dev@flink.apache.org Subject: [EXTERNAL] Plans for JDBC connector for 1.20? Hi, Is there a plan to release the JDBC for Flink 1.20

FW: Re: Flink technical debt.

ward and close out appropriately; so new contributions are looked at in the timely way. Any feedback on the approach and focus is welcome. Kind regards, David. From: David Radley Date: Thursday, 21 November 2024 at 11:56 To: dev@flink.apache.org , Robert Metzger , Tom Cooper Subject: FW: [EXTERNAL] R

RE: FW: Re: Flink technical debt.

ent commits and if there are conflicts in this PR then they also should be resolved On Thu, Nov 21, 2024 at 12:57 PM David Radley wrote: > Hi all, > We had the 1st 30 minute working meeting of the Community Health > Initiative (CHI). > > Using the git query : > https://github.co

Plans for JDBC connector for 1.20?

Hi, Is there a plan to release the JDBC for Flink 1.20? Apologies if this is already in hand, I could not find anything: * I notice that the last JDBC connector content corresponding to Flink 1.19 contained minimal content. * The main branch – now has a pom with 1.20 and contains a massi

FW: Re: Flink technical debt.

che.org/confluence/display/FLINK/1.20+Release#id-1.20Release-Syncmeeting I can give you or somebody else edit permissions in the wiki, if you tell me the username. On Thu, Nov 14, 2024 at 10:56 PM David Radley wrote: > Hi all, > We had good attendance for the kick off meeting for the Commu

RE: FW: RE: Flink technical debt.

? Cheers, Jim On Tue, Nov 19, 2024 at 6:17 AM David Radley wrote: > Hello all, > After the kick off last week for the Community Health Initiative, we > agreed to have weekly calls alternating between Eastern friendly time zones > and Western friendly time zones. > > For this wee

FW: RE: Flink technical debt.

:%22fcf67057-50c9-4ad4-98f3-ffca64add9e9%22,%22Oid%22:%229c4a6a85-e4f2-44e8-a2f2-b00cdc128be3%22%7D @Robert Metzger<mailto:rmetz...@apache.org> I will put the meeting details including the schedule on the wiki once I have access. kind regards, David. From: David Radley Date: Friday, 15 November 2

RE: Flink V1 to V2 state migration

be delighted to discuss and contribute to the flink state migration utility alongside you. Best, Xu Huang David Radley 于2024年11月12日周二 07:02写道： > Hi Gabor, > That sounds very reasonable. I will put this on my list to try, hopefully > in the next few days. > > I think the “operator

RE: Flink technical debt.

somebody else edit permissions in the wiki, if you tell me the username. On Thu, Nov 14, 2024 at 10:56 PM David Radley wrote: > Hi all, > We had good attendance for the kick off meeting for the Community Health > Initiative technical debt workgroup. > We talked of our goals being: &g

RE: Flink technical debt.

Robert is looking to attend the next meeting on the 21st. We are all hoping to appropriately take some of this work from committers / PMC members to relieve some of the burden and make this is a win for everyone 😊 . Kind regards, David. From: David Radley mailto:david_rad...@uk.ibm.com&

RE: Re: [VOTE] FLIP-440: User-defined SQL operators / ProcessTableFunction (PTF)

+1 (non-binding) kind regards, David From: Dawid Wysakowicz Date: Tuesday, 12 November 2024 at 10:47 To: dev@flink.apache.org Subject: [EXTERNAL] Re: Re: [VOTE] FLIP-440: User-defined SQL operators / ProcessTableFunction (PTF) +1 (binding) Best, Dawid On Tue, 12 Nov 2024 at 09:28, Fabian Hüske

FW: Re: Flink technical debt.

speed up the process of contributing. Cheers, Jim On Mon, Nov 11, 2024 at 5:51 PM David Radley wrote: > Hello everyone, > I would like to have a kickoff meeting this week for us all to meet. > > In general, I would like these meeting to be working meetings. But for > this first mee

RE: Flink V1 to V2 state migration

l the state types are written (this can be quite extensive so maybe try a couple first) and restore it with 2.0-preview. Sooner or later we're going to face all the issues but the sooner we see them the better. G On Mon, Nov 11, 2024 at 6:31 PM David Radley wrote: > Hello Zakelly, > Tha

RE: Flink technical debt.

for quicker collaboration. All decisions from the calls need to end up in Jira and on the mailing lists On Mon, Nov 4, 2024 at 4:07 PM David Radley wrote: > Hello, > I have been looking at the Flink Jira and git. I see a large number of > Flink Jira issues that are open and critical or

RE: Flink V1 to V2 state migration

gt; and > > see if there are more issues on this. > > > > [1] > > > > > https://nightlies.apache.org/flink/flink-docs-master/docs/libs/state_processor_api/ > > > > > > Best, > > Zakelly > > > > On Sat, Nov 9, 2024 at 12:48 AM Gale

Flink V1 to V2 state migration

Hello, At Flink Forward I learnt that Fink V1 state could not be migrated to V2. I think this would be a big migration inhibitor for current Flink users, as they would need to throw away their existing state. As such I think this is a critical possible blocking issue. Prior to Flink 2 going out,

RE: [DISCUSS] FLIP-440: User-defined SQL operators / ProcessTableFunction (PTF)

Hi Timo, Thank you for the well structured and referenced Flip. This looks really useful. Some thoughts: 1. I wonder what class of scenarios that PTF’s do not do well in and that DataStream API would be preferable/required? Assuming we have PTF Map and List support. 2. I see /** *

RE: Flink technical debt.

. no activity for a year) and set timeouts for responding. This will probably clear a large number of stale PRs and issues quickly and shrink the size of the pile that needs to be triaged. Cheers, Tom Cooper On Monday, 4 November 2024 at 15:05, David Radley wrote: > Hello, > I have

RE: Flink technical debt.

for quicker collaboration. All decisions from the calls need to end up in Jira and on the mailing lists On Mon, Nov 4, 2024 at 4:07 PM David Radley wrote: > Hello, > I have been looking at the Flink Jira and git. I see a large number of > Flink Jira issues that are open and critical or

RE: [DISCUSS] FLIP-XXX Add K8S conditions to Flink CRD

tion that captures > the upgrade process itself (if a resource is fully upgraded / reconciled) > > Cheers, > Gyula > > On Mon, Sep 23, 2024 at 12:16 PM David Radley > wrote: > > > Hi Lajith, > > The updated document is much more detailed and looks good. As you say th

Flink technical debt.

Hello, I have been looking at the Flink Jira and git. I see a large number of Flink Jira issues that are open and critical or blockers https://issues.apache.org/jira/browse/FLINK-36655?jql=project%20%3D%20FLINK%20AND%20priority%20in%20(Blocker%2C%20Critical) I realise some of these issues may not

FW: RE: Kafka connector releases

Hi again Arvid, I realise we actually have 3 releases (2 bug releases) supporting 1.18 – the renumbering threw me 😊. So I think your proposal looks good, kind regards, David. From: David Radley Date: Monday, 30 September 2024 at 17:07 To: dev@flink.apache.org Subject: [EXTERNAL] RE

RE: Kafka connector releases

e. Best, Arvid On Fri, Sep 27, 2024 at 11:11 AM David Radley wrote: > Hi Arvid, > Some thoughts on whether we need the 3 deliverables. And whether we could > follow more traditional fixpack numbering: > I see that there is already a release for 1.19 > https://mvnrepository.com/ar

Re: Kafka connector releases

Hi Arvid, Some thoughts on whether we need the 3 deliverables. And whether we could follow more traditional fixpack numbering: I see that there is already a release for 1.19 https://mvnrepository.com/artifact/org.apache.flink/flink-connector-kafka/3.2.0-1.19 . I am wondering why we need the firs

FW: RE: [DISCUSS] FLIP-XXX Apicurio-avro format

testing to confirm my understanding either way. If we can get the format name in the connector – I agree your proposed solution is neater, Warm regards, David. From: David Radley Date: Tuesday, 24 September 2024 at 22:16 To: dev@flink.apache.org Subject: [EXTERNAL] RE: [DISCUSS] FLIP-XXX

RE: [DISCUSS] FLIP-XXX Apicurio-avro format

wards compatibility. Best. Arvid PS: don't hesitate to reach out on slack for quicker feedback. we should still primarily use the ML to keep everyone in the loop but it's usually much faster to ping me there if you post an answer here. On Tue, Sep 24, 2024 at 7:50 PM Robert Metzger wrote:

RE: [DISCUSS] FLIP-XXX Add K8S conditions to Flink CRD

gt; the >> > job status but one could argue that it was "designed" this way. >> > >> > I think we should probably have more condition types to capture the >> > difference: >> > - JobReady (True/False) -> Flink job is running (Basically job status >

Non-nullable children of nullable arrays and objects in SQL not working with Avro format

Hi, I have been looking at an issue where non-nullable children under nullable objects or arrays does not work. I identified the issue to be Calcite that enforces this nullability. More details are in https://issues.apache.org/jira/browse/CALCITE-6579 It seems most SQLs do not support having no

Flink Releases

Hi, I notice that https://nightlies.apache.org/flink/flink-docs-master/versions/ does not include 1.20. It seems that {{< all_versions >}} is not picking it up. I am happy to make the change, but could not see where to, Kind regards, David. Unless otherwise stated above: IBM Uni

Match recognize references old type system in docs.

Hi , I notice in the first example. https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/queries/match_recognize/ In the create table for Ticker, it refers to deprecated TimeIndicatorTypeInfo : |-- rowtime: TimeIndicatorTypeInfo(rowtime) # point in time when the change to th

RE: Flink aggregation docs

d the behavior of windowing, we simplify the displaying of timestamp values to not show the trailing zeros, e.g. 2020-04-15 08:05 should be displayed as 2020-04-15 08:05:00.000 in Flink SQL Client if the type is TIMESTAMP(3).* Best regards, Martijn On Fri, Aug 30, 2024 at 1:22 PM David Radley wrote:

Flink aggregation docs

Hi , I am looking at https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/queries/window-tvf/ and tried to follow the instructions, but it was not as I expected. I created a javascript program to populate a table defined as per the docs in the Tumble section. Unfortunately ti

[DISCUSS] FLIP-319: Integrating with Kafka’s proper support for 2PC participation (KIP-939).

Hi, I just watched the Flink forward session on the Ververica web site round this and think this is a good issue to have fixed. I wonder: * What is the state of this Flip – is it close to going forward to vote? * I assume the existing java reflection might have issues with later Java (v

RE: [VOTE] FLIP-473: Introduce New SQL Operators Based on Asynchronous State APIs

+1 (non-binding) Kind regards, David. From: Lincoln Lee Date: Thursday, 22 August 2024 at 03:35 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [VOTE] FLIP-473: Introduce New SQL Operators Based on Asynchronous State APIs +1 (binding) Best, Lincoln Lee Feng Jin 于2024年8月22日周四 09:44写道： > +

RE: [DISCUSS] FLIP-XXX Apicurio-avro format

, 25 July 2024 at 16:46 To: dev@flink.apache.org Cc: David Radley Subject: [EXTERNAL] Re: [DISCUSS] FLIP-XXX Apicurio-avro format Hey, Thanks for the updated FLIP. > 1. 20 or beyond Given this is intended to go in the Kafka connector we can target the next Kafka connector version (v3.  3. 0)

RE: Potential Kafka Connector FLIP: Large Message Handling

eap sizes would be worth considering. Yes, we're implementing the 'claim check' pattern and this is definitely something we're considering! Thanks for raising it On Wed, Jul 10, 2024 at 11:06 AM David Radley mailto:david_rad...@uk.ibm.com>> wrote: Hi Kevin, You mention t

Supporting fields containing "." in watermark

Hi there, It looks like Flink does not support fields containing a dot character in the watermark. The validation done on Flink code to determine whether the property is "nested", is to check if they contain a dot in the name, so even if the property is not nested, but contains a dot, it is rep

RE: [DISCUSS] FLIP-XXX Apicurio-avro format

://cwiki.apache.org/confluence/display/FLINK/FLIP-454%3A+New+Apicurio+Avro+format As the design is significantly different, there will be a new period of discussion before going to vote. Fyi I will be on vacation after this week until the 13th of August. Kind regards, David. From: David Radley Date

RE: [VOTE] FLIP-465: Introduce DESCRIBE FUNCTION

+1 (non-binding) Kind regards , David. From: Martijn Visser Date: Thursday, 11 July 2024 at 10:10 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [VOTE] FLIP-465: Introduce DESCRIBE FUNCTION +1 (binding) On Sat, Jul 6, 2024 at 6:52 PM Yubin Li wrote: > +1 (non-binding) > > Best, > Yubin > >

RE: Potential Kafka Connector FLIP: Large Message Handling

Hi Kevin, You mention the link https://www.conduktor.io/kafka/how-to-send-large-messages-in-apache-kafka/#Option-1:-using-an-external-store-(GB-size-messages)-0 , I assume this is the approach you are considering. And that this is being done at the connector level, as the message could be in any

RE: [DISCUSS] FLIP-XXX Apicurio-avro format

Message Header support? I am also interested in supporting headers with the Flink SQL Formats: https://lists.apache.org/thread/spl88o63sjm2dv4l5no0ym632d2yt2o6 On Fri, Jun 14, 2024 at 6:10 AM David Radley wrote: > Hi everyone, > I have talked with Chesnay and Danny offline. Danny and I were no

Re: [2.0] How to handle on-going feature development in Flink 2.0?

Hi, I think this is a great question. I am not sure if this has been covered elsewhere, but it would be good to be clear how this effects the connectors and operator repos, with potentially v1 and v2 oriented new featuresI suspect this will be a connector by connector investigation. I am thinkin

FW: Non Nullable fields within objects

Hi, I am looking to get the Avro format to support Non Nullable fields within objects or arrays. It works with Confluent Avro. I notice https://issues.apache.org/jira/browse/CALCITE-4085 where it looks like Calcite was changed to allow this capability to work with Flink. https://github.com/apac

Re: [ANNOUNCE] New Apache Flink Committer - Zhongqiang Gong

Congratulations Zhongqiang, Kind regards, David. From: Feng Jin Date: Monday, 17 June 2024 at 12:36 To: dev@flink.apache.org Subject: Re: [ANNOUNCE] New Apache Flink Committer - Zhongqiang Gong Congratulations Zhongqiang !!! Best regards Feng Jin On Mon, Jun 17, 2024 at 7:01 PM Feifan Wang w

RE: [DISCUSS] FLIP-XXX Apicurio-avro format

Flink interfaces. I am going to prototype this idea. WDYT? My thanks go to Chesnay and Danny for their support and insight around this Flip, Kind regards, David. From: David Radley Date: Wednesday, 29 May 2024 at 11:39 To: dev@flink.apache.org Subject: [EXTERNAL] RE: [DISCUSS] FLIP-XXX

RE: [VOTE] Release flink-connector-kafka v3.2.0, release candidate #1

ector 4.0, not for 3.2.0. It's not related to this release. Best regards, Martijn On Tue, Jun 11, 2024 at 3:54 PM David Radley wrote: > Hi, > Sorry I am a bit late. > I notice https://issues.apache.org/jira/browse/FLINK-35109 is open and a > blocker. Can I confirm that we have

RE: [VOTE] Release flink-connector-kafka v3.2.0, release candidate #1

Hi, Sorry I am a bit late. I notice https://issues.apache.org/jira/browse/FLINK-35109 is open and a blocker. Can I confirm that we have mitigated the impacts of this issue in this release? Kind regards, David. From: Danny Cranmer Date: Friday, 7 June 2024 at 11:46 To: dev@flink.apache.org

RE: Flink Kubernetes Operator 1.9.0 release planning

I agree – thanks for driving this Gyula. From: Rui Fan <1996fan...@gmail.com> Date: Tuesday, 11 June 2024 at 02:52 To: dev@flink.apache.org Cc: Mate Czagany Subject: [EXTERNAL] Re: Flink Kubernetes Operator 1.9.0 release planning Thanks Gyula for driving this release! > I suggest we cut the rel

Re: [DISCUSS] Connector Externalization Retrospective

Hi Danny, I think your proposal is a good one. This is the approach that we took with the Egeria project, firstly taking the connectors out of the main repo, then connectors having their own versions that incremented organically rather then tied to the core release. Blue sky thinking - I wonder

RE: [ANNOUNCE] New Apache Flink PMC Member - Fan Rui

Congratulations, Rui! From: Sergey Nuyanzin Date: Sunday, 9 June 2024 at 20:33 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [ANNOUNCE] New Apache Flink PMC Member - Fan Rui Congratulations, Rui! On Fri, Jun 7, 2024 at 5:36 AM Xia Sun wrote: > Congratulations, Rui! > > Best, > Xia > > Paul

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

Hi Sergio, Sounds good . I am relatively new to this area and had some basic questions: I notice in [1] it talks of materialized views. And CREATE view can already take the AS keyword. It would be useful to me to understand when we would use each of these. - I assume the table will be kept up t

RE: [DISCUSS] FLIP-XXX Add K8S conditions to Flink CRD

etc). > > These 2 conditions should be enough to start with and would actually > provide a tangible value to users. We can probably leave out ClusterReady > on a second thought. > > Cheers, > Gyula > > > On Wed, May 29, 2024 at 5:16 PM David Radley > wrote: > >

RE: [DISCUSS] FLIP-XXX Add K8S conditions to Flink CRD

tatus fields. But maybe thats not a problem or a way to eliminate the old fields later? I am not so sure of the Error status and what this means in practice. Why do we want to track the last error in 2 places? It's already in the status. What do you think? Gyula On Wed, May 29, 2024 at 3:55 PM Dav

Re: [DISCUSS] FLIP-XXX Add K8S conditions to Flink CRD

Hi, Thanks Lajith for raising this discussion thread under the Flip title. To summarise the concerns from the other discussion thread. “ - I echo Gyula that including some examples and further explanations might ease reader's work. With the current version, the FLIP is a bit hard to follow. - W

RE: [DISCUSS] FLIP-XXX Apicurio-avro format

better option. I would be interested to hear if others have any suggestions. Playing devil's advocate against myself, we pass maps around to configure connectors so it is not too far away from that. Thanks, Danny On Fri, May 24, 2024 at 2:23 PM David Radley wrote: > Hi Danny, > No wo

RE: [DISCUSS] Proposing an LTS Release for the 1.x Line

causing the overall stability to > be degraded. I think our starting point should be "We don't backport > features, unless discussed and agreed on the Dev mailing list". That still > opens up the ability to backport features but makes it clear where the bar > lies. >

RE: [DISCUSS] FLIP-XXX Apicurio-avro format

this way? Thanks, Danny On Wed, May 22, 2024 at 3:43 PM David Radley wrote: > Hi Danny, > Did you have a chance you have a look at my responses to your feedback? I > am hoping to keep the momentum going on this one, kind regards, David. > > > From: David Radley >

RE: [DISCUSS] Proposing an LTS Release for the 1.x Line

Hi, I agree with Martijn that we only put features into version 2. Back porting to v1 should not be business as usual for features, only for security and stability changes. If there is a maintainer willing to merge backported features to v1, as it is important to some part of the community, thi

Re: [DISCUSS] FLIP-XXX Apicurio-avro format

Hi Danny, Did you have a chance you have a look at my responses to your feedback? I am hoping to keep the momentum going on this one, kind regards, David. From: David Radley Date: Tuesday, 14 May 2024 at 17:21 To: dev@flink.apache.org Subject: [EXTERNAL] [DISCUSS] FLIP-XXX Apicurio-avro

RE: [DISCUSSION] FLIP-450: Improve Runtime Configuration for Flink 2.0

Hi Xuannan, I like that you are cleaning up options that I assume are not recommended or currently used in some way. I have not got experience of these options. For the proposed deprecations, will there be a proposed recommended alternatives that will be mentioned in the deprecation. If they ar

RE: [VOTE] FLIP-454: New Apicurio Avro format

st class support for Avro and Apicurio > > > > > > -- Mark Nuttall, mnutt...@apache.org > > > Senior Software Engineer, IBM Event Automation > > > > > > On 2024/05/02 09:41:09 David Radley wrote: > > > > Hi everyone, > > > > > > > &g

[DISCUSS] FLIP-XXX Apicurio-avro format

Hi Danny, Thank you very much for the feedback and your support. I have copied your feedback from the VOTE thread to this discussion thread, so we can continue our discussions off the VOTE thread. Your feedback: Thanks for Driving this David. I am +1 for adding support for the new format, h

RE: [VOTE] FLIP-451: Introduce timeout configuration to AsyncSink

Regards Ahmed Hamdy On Mon, 13 May 2024 at 16:21, David Radley wrote: > Hi, > I raised a question on the discussion thread, around retriable errors, as > a possible alternative, > Kind regards, David. > > > From: Aleksandr Pilipenko > Date: Monday, 13 May

RE: [VOTE] FLIP-451: Introduce timeout configuration to AsyncSink

Hi, I raised a question on the discussion thread, around retriable errors, as a possible alternative, Kind regards, David. From: Aleksandr Pilipenko Date: Monday, 13 May 2024 at 16:07 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [VOTE] FLIP-451: Introduce timeout configuration to As

RE: [DISCUSS] FLIP-451: Refactor Async sink API

Hi, I wonder if the way that the async request fails could be a retriable or non-retriable error, so it would retry only for retriable (transient) errors (like IOExceptions) . I see some talk on the internet around retriable SQL errors. If this was the case then we may need configuration to lim

RE: Discussion: Condition field in the CR status

Hi Lajith, This idea for a Flip is a good addition, which I support. As discussed: These conditions populate a status field in the K8s UI – Openshift in our case. Currently the status does not contain any information. With the conditions present, the status will be populated with meaningful inf

RE: [RESULT][VOTE] FLIP-454: New Apicurio Avro format

FLIP forward, but we need 3 +1(binding) votes according Flink Bylaws[1] before community accepted it. Best, Leonard [1] https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws > 2024??5??8?? 11:05??David Radley ?? > > Hi everyone, > I am happy to say that FLIP-454:

[RESULT][VOTE] FLIP-454: New Apicurio Avro format

Hi everyone, I am happy to say that FLIP-454: New Apicurio Avro format [1] has been accepted and voted through this thread [2]. The proposal has been accepted with 4 approving votes and there are no vetos: - Ahmed Hamdy (non-binding) - Jeyhun Karimov (non-binding) - Mark Nuttall (non-binding) -

[jira] [Created] (FLINK-35311) FLIP-454: New Apicurio Avro format

david radley created FLINK-35311: Summary: FLIP-454: New Apicurio Avro format Key: FLINK-35311 URL: https://issues.apache.org/jira/browse/FLINK-35311 Project: Flink Issue Type: Improvement

RE: FW: RE: [DISCUSS] FLIP-XXX Apicurio-avro format

Hi Martijn, I have started a vote thread – please could you update the Flip with the link to the vote thread, Kind regards, David. From: David Radley Date: Thursday, 2 May 2024 at 10:39 To: dev@flink.apache.org Subject: [EXTERNAL] RE: FW: RE: [DISCUSS] FLIP-XXX Apicurio-avro format

[VOTE] FLIP-454: New Apicurio Avro format

Hi everyone, I'd like to start a vote on the FLIP-454: New Apicurio Avro format [1]. The discussion thread is here [2]. The vote will be open for at least 72 hours unless there is an objection or insufficient votes. [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-454%3A+New+Apicurio+

RE: FW: RE: [DISCUSS] FLIP-XXX Apicurio-avro format

Fabulous, thanks Martijn 😊 From: Martijn Visser Date: Thursday, 2 May 2024 at 10:08 To: dev@flink.apache.org Subject: [EXTERNAL] Re: FW: RE: [DISCUSS] FLIP-XXX Apicurio-avro format Done :) On Thu, May 2, 2024 at 11:01 AM David Radley wrote: > Hi Martijn, > Thank you very much for look

RE: FW: RE: [DISCUSS] FLIP-XXX Apicurio-avro format

, I've copied and pasted it into https://cwiki.apache.org/confluence/display/FLINK/FLIP-454%3A+New+Apicurio+Avro+format; please take a look if it's as expected. Best regards, Martijn On Wed, May 1, 2024 at 3:47 PM David Radley wrote: > Hi Martijn, > Any news? >

FW: RE: [DISCUSS] FLIP-XXX Apicurio-avro format

Hi Martijn, Any news? Kind regards, David. From: David Radley Date: Monday, 22 April 2024 at 09:48 To: dev@flink.apache.org Subject: FW: [EXTERNAL] RE: [DISCUSS] FLIP-XXX Apicurio-avro format Hi Martijn, A gentle nudge, is this ok for you or one of the PMC or committers to create a

FW: RE: [DISCUSS] FLIP-XXX Apicurio-avro format

Hi Martijn, A gentle nudge, is this ok for you or one of the PMC or committers to create a Flip now? Kind regards, David. From: David Radley Date: Monday, 15 April 2024 at 12:29 To: dev@flink.apache.org Subject: Re: [EXTERNAL] RE: [DISCUSS] FLIP-XXX Apicurio-avro format Hi Martijn

RE: [DISCUSS] FLINK-34440 Support Debezium Protobuf Confluent Format

a new schemaID, if the user specifies an explicit schemaID we just use it directly? Thanks Anupam On Wed, Apr 10, 2024 at 2:27 PM David Radley wrote: > Hi, > I notice in the draft pr that there is a schema id in the format config. I > was wondering why? In the confluent avro and

Re: [EXTERNAL] RE: [DISCUSS] FLIP-XXX Apicurio-avro format

n On Fri, Apr 12, 2024 at 6:08 PM David Radley wrote: > Hi, > A gentle nudge. Please could a committer/PMC member raise the Flip for > this, > Kind regards, David. > > > From: David Radley > Date: Monday, 8 April 2024 at 09:40 > To: dev@flink.apache.org > Sub

  1   2   >