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

. If they are going to be removed for v2, it would be good to explicitly document the thinking and impact of the deprecations and consequent removals, Kind regards, David. From: Xuannan Su Date: Tuesday, 14 May 2024 at 02:08 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [DISCUSSION] FLIP-450

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

Hi Danny, Thankyou so much for supporting this flip and for your feedback. I have copied your points and responded on the discussion thread here: https://lists.apache.org/thread/rmcc67z35ysk0sv2jhz2wq0mwzjorhjb kind regards, David. From: Danny Cranmer Date: Tuesday, 14 May 2024 at 11:58

[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

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

Thanks for the clarification Ahmed +1 (non-binding) From: Ahmed Hamdy Date: Monday, 13 May 2024 at 19:58 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [VOTE] FLIP-451: Introduce timeout configuration to AsyncSink Thanks David, I have replied to your question in the discussion thread. Best

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

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

to limit the number of retries of retriable errors. Kind regards, David From: Muhammet Orazov Date: Monday, 13 May 2024 at 10:30 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [DISCUSS] FLIP-451: Refactor Async sink API Great, thanks for clarifying! Best, Muhammet On 2024-05-06 13

RE: Discussion: Condition field in the CR status

, maybe rolledback, deployed or stable? We also talked of whether there are any use cases would be beneficial, at this time we don’t think so – but you said you have a look at this, Kind regards, David, From: Lajith Koova Date: Monday, 13 May 2024 at 10:29 To: dev@flink.apache.org Subject

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

Hi Leonard, OK thanks ?C I missed that. Are any committers/PMC members prepared to back this Flip? Kind regards, David. From: Leonard Xu Date: Wednesday, 8 May 2024 at 16:43 To: dev Subject: [EXTERNAL] Re: [RESULT][VOTE] FLIP-454: New Apicurio Avro format Thanks David for driving

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

the changes? [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-454%3A+New+Apicurio+Avro+format [2] https://lists.apache.org/list?dev@flink.apache.org:lte=1M:apicurio Thanks to all involved. Kind regards, David Unless otherwise stated above: IBM United Kingdom Limited Registered

[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

+Avro+format [2] https://lists.apache.org/thread/wtkl4yn847tdd0wrqm5xgv9wc0cb0kr8 Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

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 l

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

and verbose. Please could you replace the Flip with content from the above link, Kind regards, David, From: Martijn Visser Date: Wednesday, 1 May 2024 at 16:31 To: dev@flink.apache.org Subject: [EXTERNAL] Re: FW: RE: [DISCUSS] FLIP-XXX Apicurio-avro format Hi David

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

Flink stateful functions and Agentic Architecture

like langchain or langgraph. Such a system could be multi-tenant and fully scalable. I wonder if anyone has explored using Flink stateful functions i this way of has suggestion of examples to look at for similar use cases? -- David Carroll Chief of Research & Development <http://spotter.

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

are compatible with the confluent avro format. WDYT? Kind regards, David. From: Anupam Aggarwal Date: Saturday, 13 April 2024 at 16:08 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [DISCUSS] FLINK-34440 Support Debezium Protobuf Confluent Format Hi David, Thank you for the suggestion

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

. If this it too much or too little, I can amend, Kind regards, David. From: Martijn Visser Date: Friday, 12 April 2024 at 18:11 To: dev@flink.apache.org Subject: Re: [EXTERNAL] RE: [DISCUSS] FLIP-XXX Apicurio-avro format Hi David, I tried, but the format wasn't as the FLIP template expects

[jira] [Created] (FLINK-35097) Table API Filesystem connector with 'raw' format repeats last line

David Perkins created FLINK-35097: - Summary: Table API Filesystem connector with 'raw' format repeats last line Key: FLINK-35097 URL: https://issues.apache.org/jira/browse/FLINK-35097 Project: Flink

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

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 Subject: [EXTERNAL] RE: [DISCUSS] FLIP-XXX Apicurio-avro format Hi, I have posted a Google Doc [0

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

schemas are registered. I would suggest aiming to copy what the confluent DeSer libraries do rather than having a schema id hard coded in the config. WDYT? Kind regards, David. From: Kevin Lam Date: Tuesday, 26 March 2024 at 20:06 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [DISCUSS

RE: [DISCUSS] FLIP-437: Support ML Models in Flink SQL

. It would be interesting to see how champion challenger scenarios would play out – when you try a new version of the model that might perform better. I suggest having a new optional model-version keyword, which would seem to be a cleaner way of specifying a model. Kind regards, David. From

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

the process [1], Kind regards, David. [0] https://docs.google.com/document/d/14LWZPVFQ7F9mryJPdKXb4l32n7B0iWYkcOdEd1xTC7w/edit?usp=sharing [1] https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals#FlinkImprovementProposals-CreateyourOwnFLIP From: Jeyhun Karimov Date

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

. [1] https://docs.google.com/document/d/14LWZPVFQ7F9mryJPdKXb4l32n7B0iWYkcOdEd1xTC7w/edit?usp=sharing Kind regards, David From: David Radley Date: Wednesday, 20 March 2024 at 11:03 To: dev@flink.apache.org Subject: [EXTERNAL] [DISCUSS] FLIP-XXX Apicurio-avro format Hi, As per the FLIP

Re: [VOTE] FLIP-437: Support ML Models in Flink SQL

. Best, D. On Wed, Apr 3, 2024 at 2:31 AM David Radley wrote: > Hi Hao, > I don’t think this counts as an objection, I have some comments. I should > have put this on the discussion thread earlier but have just got to this. > - I suggest we can put a model version in the model resour

Re: [VOTE] FLIP-437: Support ML Models in Flink SQL

in via a new connector could be kept up to date with the external model and would not be allowed to be changed by anything other than the connector. Kind regards, David. From: Hao Li Date: Friday, 29 March 2024 at 16:30 To: dev@flink.apache.org Subject: [EXTERNAL] [VOTE] FLIP-437: Support ML

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

/java/org/apache/flink/formats/avro/RegistryAvroDeserializationSchema.java#L109 Then this should work. Does this address your question? Kind regards, David. From: Jeyhun Karimov Date: Thursday, 21 March 2024 at 21:06 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [DISCUSS] FLIP-XXX

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

to work with content IDs as well as global IDs. In line with the deser Apicurio IdHandler and headerHandlers. kind regards, David. On 2024/03/20 15:18:37 Mark Nuttall wrote: > +1 to this > > A few small comments: > > Currently, if users have Avro schemas in an Apicurio Re

[DISCUSS] FLIP-XXX Apicurio-avro format

prototyped a lot of the content to prove that this approach is feasible. I look forward to the discussion, Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth

RE: Additional metadata available for Kafka serdes

deserialization or serialization? The only place I could see it being used could be in serialization, where we register a (potentially new) schema, but this may not be desired as the schema could be a nested schema. WDYT kind regards, David. From: Balint Bene Date: Thursday, 14 March 2024 at 20:16

RE: [ANNOUNCE] Apache Flink 1.19.0 released

Congratulations! Kind regards, David From: Ahmed Hamdy Date: Monday, 18 March 2024 at 15:55 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [ANNOUNCE] Apache Flink 1.19.0 released Congratulations! Best Regards Ahmed Hamdy On Mon, 18 Mar 2024 at 12:30, Xintong Song wrote: > Congratulati

Re: Additional metadata available for Kafka serdes

this approach will meet your needs, Kind regards, David. From: Balint Bene Date: Tuesday, 12 March 2024 at 22:18 To: dev@flink.apache.org Subject: [EXTERNAL] Additional metadata available for Kafka serdes Hello! Looking to get some guidance for a problem around the Flink formats used for Kafka

[jira] [Created] (FLINK-34647) Path normalization is allocation intensive

David Schlosnagle created FLINK-34647: - Summary: Path normalization is allocation intensive Key: FLINK-34647 URL: https://issues.apache.org/jira/browse/FLINK-34647 Project: Flink Issue

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

object. I also wondered whether these Kafka only formats should be moved to the Kafka connector repo, or whether they might in the future be used outside Kafka – e.g. Avro/Protobuf files in a database. Kind regards, David. From: Kevin Lam Date: Wednesday, 21 February 2024 at 18:51 To: dev

[jira] [Created] (FLINK-34477) support capture groups in REGEXP_REPLACE

David Anderson created FLINK-34477: -- Summary: support capture groups in REGEXP_REPLACE Key: FLINK-34477 URL: https://issues.apache.org/jira/browse/FLINK-34477 Project: Flink Issue Type

RE: [ANNOUNCE] New Apache Flink Committer - Jiabao Sun

Congratulations Jiabao! From: Swapnal Varma Date: Monday, 19 February 2024 at 10:14 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [ANNOUNCE] New Apache Flink Committer - Jiabao Sun Congratulations Jiabao! Best, Swapnal On Mon, 19 Feb 2024, 15:37 weijie guo, wrote: > Congratulations,

FLINK-21672

by removing the dependency on this old / unsupported sun package . I am happy to work on this, if you are willing to support this by assigning me the Jira and merging the fix; ideally we would like this to be in the next release - Flink 1.19, Kind regards, David. Unless otherwise stated above

RE: Issues running with Flink 1.20-SNAPSHOT

Hi Martijn, Yes the Maven wrapper works, so it is a local issue. Thank you for the pointer, I am glad it is not anything serious, Kind regards, David. From: Martijn Visser Date: Friday, 9 February 2024 at 16:27 To: dev@flink.apache.org Subject: [EXTERNAL] Re: Issues running with Flink

Issues running with Flink 1.20-SNAPSHOT

ncoding: UTF-8 OS name: "mac os x", version: "14.2.1", arch: "aarch64", family: "mac" It looks like the new snapshot is not completely there. I was expecting to see a folder for flink-dist-scala_2.12:jar similar to https://repository.apache.org/content/

RE: FW: RE: [VOTE] Release flink-connector-jdbc, release candidate #3

;Sergey Nuyanzin snuyan...@gmail.com<mailto:snuyan...@gmail.com>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. I assume the warning is ok, Kind regards, David. From: Sergey

FW: RE: [VOTE] Release flink-connector-jdbc, release candidate #3

regards, David. From: David Radley Date: Thursday, 8 February 2024 at 10:46 To: dev@flink.apache.org Subject: [EXTERNAL] RE: [VOTE] Release flink-connector-jdbc, release candidate #3 +1 (non-binding) I assume that thttps://github.com/apache/flink-web/pull/707 and be completed after the release

RE: Flink jdbc connector rc3 for flink 1.18

Hi Sergey, Yes that makes sense, thanks, Kind regards, David. From: Sergey Nuyanzin Date: Wednesday, 7 February 2024 at 11:41 To: dev@flink.apache.org Subject: [EXTERNAL] Re: Flink jdbc connector rc3 for flink 1.18 Hi David, Thanks for testing. Yes the jars are built from the same sources

RE: [VOTE] Release flink-connector-jdbc, release candidate #3

+1 (non-binding) I assume that thttps://github.com/apache/flink-web/pull/707 and be completed after the release is out. From: Martijn Visser Date: Friday, 2 February 2024 at 08:38 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [VOTE] Release flink-connector-jdbc, release candidate #3 +1

Flink jdbc connector rc3 for flink 1.18

– unless the connector is released very soon – and we would pick that up. Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

FW: RE: Flink JDBC connector release

Hi Sergey, It looks like the issue we saw was a caused by a mismatch in our build levels, so was a false negative; and is not an issue. We are testing with the latest level of the branch now (the one compiled against 1.16). Kind regards, David. From: David Radley Date: Sunday, 4 February

FW: RE: Flink JDBC connector release

Hi Sergey, Sorry for the typos. I meant: Yes that is right, I am talking about the jdbc connector rc3 and Flink 1.18. I am looking into finding a simple way to reproduce the issue, and will raise a Jira if I can, Kind regards, David. From: Sergey Nuyanzin Date: Friday, 2 February 2024

RE: Flink JDBC connector release

Hi Sergey, Yes that is right I am talking about are talking about jdbc connector rc3 and Flink 1.18. I am looking into finding a simple way to reproduce it, and will raise a Jira if I can, Kind regards, David. From: Sergey Nuyanzin Date: Friday, 2 February 2024 at 19:46 To: dev

Flink JDBC connector release

Hi, We have been doing some testing on flink jdbc connector rc2. We are testing with Flink 1.1.8 jars and are using the TableEnvironment TableResult

Re: [VOTE] Release flink-connector-jdbc, release candidate #2

JDBC java 17 support (FLINK-33787) be included in this release? * The Flink version in the pom is 1.17, but we are saying we support Flink 1.16. Kind regards, David. From: Sergey Nuyanzin Date: Tuesday, 30 January 2024 at 00:18 To: dev@flink.apache.org Subject: [EXTERNAL] [VOTE] Release

[jira] [Created] (FLINK-34252) WatermarkAssignerOperator should not emit WatermarkStatus.IDLE under continuous data flow

David Christle created FLINK-34252: -- Summary: WatermarkAssignerOperator should not emit WatermarkStatus.IDLE under continuous data flow Key: FLINK-34252 URL: https://issues.apache.org/jira/browse/FLINK-34252

[jira] [Created] (FLINK-34211) Filtering on Column names with ?s fails for JDBC lookup join.

david radley created FLINK-34211: Summary: Filtering on Column names with ?s fails for JDBC lookup join. Key: FLINK-34211 URL: https://issues.apache.org/jira/browse/FLINK-34211 Project: Flink

[jira] [Created] (FLINK-34170) Include the look up join conditions in the optimised plan.

david radley created FLINK-34170: Summary: Include the look up join conditions in the optimised plan. Key: FLINK-34170 URL: https://issues.apache.org/jira/browse/FLINK-34170 Project: Flink

[jira] [Created] (FLINK-34146) JDBC lookup joins fail with RDB column names containing colons

david radley created FLINK-34146: Summary: JDBC lookup joins fail with RDB column names containing colons Key: FLINK-34146 URL: https://issues.apache.org/jira/browse/FLINK-34146 Project: Flink

Re: [DISCUSS] FLIP-388: Support Dynamic Logger Level Adjustment

Hi Yuepeng, Thanks for the FLIP! There was already quite a discussion on FLIP-210 [1][2], that has proposed more or less the same thing. FLIP was marked as out of scope for Flink because underlying technologies already address it. Are you aware of the effort? If yes, what has changed since then?

Re: FW: [ANNOUNCE] New Apache Flink Committer - Alexander Fedulov

t;> > > > > >> Best, > > > > >> Junrui > > > > >> > > > > >> weijie guo 于2024年1月4日周四 09:57写道： > > > > >> > > > > >>> Congratulations, Alex! > > > > >>> &g

Re: [DISCUSS] FLIP 411: Chaining-agnostic Operator ID generation for improved state compatibility on parallelism change

Hi Zhanghao, Thanks for the FLIP. What you're proposing makes a lot of sense +1 Have you thought about how this works with unaligned checkpoints in case you go from unchained to chained? I think it should be fine because this scenario should only apply to forward/rebalance scenarios where we, as

Re: [DISCUSS] FLIP-413: Enable unaligned checkpoints by default

ocs/ops/state/checkpoints_vs_savepoints/#capabilities-and-limitations David On Fri, Jan 5, 2024 at 5:42 AM Piotr Nowojski wrote: > Ops, fixing the topic. > > Hi! > > > > I would like to propose by default to enable unaligned checkpoints and > > also simultaneously incre

RE: [VOTE] Release flink-connector-jdbc, release candidate #1

connector. I can then work on fixing the remaining FLINK-33365 query cases, which should not take too long, but I am out until Thursday this week so will be looking at it then, Kind regards, David. From: Martijn Visser Date: Friday, 5 January 2024 at 14:24 To: dev@flink.apache.org Subject

FW: [ANNOUNCE] New Apache Flink Committer - Alexander Fedulov

Sorry for my typo. Many congratulations Alex! From: David Radley Date: Wednesday, 3 January 2024 at 10:23 To: David Anderson Cc: dev@flink.apache.org Subject: Re: [EXTERNAL] [ANNOUNCE] New Apache Flink Committer - Alexander Fedulov Many Congratulations David . From: Maximilian Michels Date

Re: [ANNOUNCE] New Apache Flink Committer - Alexander Fedulov

Many Congratulations David . From: Maximilian Michels Date: Tuesday, 2 January 2024 at 12:16 To: dev Cc: Alexander Fedulov Subject: [EXTERNAL] [ANNOUNCE] New Apache Flink Committer - Alexander Fedulov Happy New Year everyone, I'd like to start the year off by announcing Alexander Fedulov

Re: [ANNOUNCE] New Apache Flink Committer - Alexander Fedulov

That's great news. Congratulations, Alex! David On Tue, Jan 2, 2024 at 9:00 AM Ryan Skraba wrote: > Awesome news for the community -- congratulations Alex (and Happy New > Year everyone!) > > Ryan > > On Tue, Jan 2, 2024 at 2:55 PM Yun Tang wrote: > > > > Congra

Re: [DISCUSS] FLIP-400: AsyncScalarFunction for asynchronous scalar function support

I'm delighted to see the progress on this. This is going to be a major enabler for some important use cases. The proposed simplifications (global config and ordered mode) for V1 make a lot of sense to me. +1 David On Wed, Dec 20, 2023 at 12:31 PM Alan Sheinberg wrote: > Tha

[jira] [Created] (FLINK-33884) Update Pulsar dependency to 3.0.2 in Pulsar Connector

David Christle created FLINK-33884: -- Summary: Update Pulsar dependency to 3.0.2 in Pulsar Connector Key: FLINK-33884 URL: https://issues.apache.org/jira/browse/FLINK-33884 Project: Flink

Re: [DISCUSS] FLIP-377: Support configuration to disable filter push down for Table/SQL Sources

Hi, I had a 3 of comments: - the name of the config option is "scan.filter-push-down.enabled". This implies it is only for scan sources and not lookups. I suggest removing the scan. prefix. - there is a talk of having a numeric option, as the filter pushdown might result in a full table scan.

Question on lookup joins

Hi , I am working on FLINK-33365 which related to JDBC predicate pushdown. I want to ensure that the same results occur with predicate pushdown as without. So I am asking this question outside the pr / issue. I notice the following behaviour for lookup joins without predicate pushdown. I was

Building Flink JDBC connector locally on M1 Mac

ing rancher, so do have a docker environment. Any pointers? Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

FW: Re: flink-sql-connector-jdbc new release

the blocking issue; it has had some reviews and one approval; please could someone either merge or provide feedback as to what needs to be changed so it can be merged, Kind regards, David. From: David Radley Date: Friday, 27 October 2023 at 16:22 To: dev@flink.apache.org Subject: Re

Re: [DISCUSS] FLIP-392: Deprecate the Legacy Group Window Aggregation

that we need to provide replacements for these internal, experimental features before officially deprecating the legacy group window aggregations, and I'd rather not wait. However, I'd be delighted to see a proposal for what that might look like. Best, David On Mon, Dec 4, 2023 at 12:45 PM Feng Jin

RE: [VOTE] FLIP-384: Introduce TraceReporter and use it to create checkpointing and recovery traces

+1(non-binding) From: Stefan Richter Date: Wednesday, 29 November 2023 at 09:44 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [VOTE] FLIP-384: Introduce TraceReporter and use it to create checkpointing and recovery traces +1 (binding) Best, Stefan > On 22. Nov 2023, at 11:20, Roman

RE: Apicurio Avro format proposal

a main feature they both do, that is relevant to Flink. Does this help? If I have misrepresented anything – please let me know, I am investigating further so I can create a well described FLIP for the proposed change, Kind regards, David. From: Ryan Skraba Date: Thursday, 23 Novembe

RE: Apicurio Avro format proposal

Hi Martijn, Ok will do, Kind regards, David. From: Martijn Visser Date: Wednesday, 22 November 2023 at 21:47 To: dev@flink.apache.org Subject: [EXTERNAL] Re: Apicurio Avro format proposal Hi David, Can you create a small FLIP for this? Best regards, Martijn On Wed, Nov 22, 2023 at 6

Re: [VOTE] FLIP-384: Introduce TraceReporter and use it to create checkpointing and recovery traces

+1 (binding) Best, D. On Wed, Nov 22, 2023 at 11:21 AM Roman Khachatryan wrote: > +1 (binding) > > Regards, > Roman > > On Wed, Nov 22, 2023, 7:08 AM Zakelly Lan wrote: > > > +1(non-binding) > > > > Best, > > Zakelly > > > > On Wed, Nov 22, 2023 at 3:04 PM Hangxiang Yu > wrote: > > > > > +1

Apicurio Avro format proposal

/getting-started/assembly-configuring-kafka-client-serdes.html#registry-serdes-types-avro_registry I am happy to work on this, Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North

Re: Proposal for Implementing Keyed Watermarks in Apache Flink

only one watermark (vanilla/global watermark), we > changed > > the API to allow moving the keyBy() before the > > assignTimestampsAndWatermarks() so the stream will be partitioned then > the > > TimestampsAndWatermarkOperator will handle the generation of each > watermark >

Re: [DISCUSS] REST API behaviour when user main method throws error

Hi Danny, > My current proposal is that the REST API should not leave the Flink cluster in an inconsistent state. Regarding consistency, Flink only cares about individual jobs, but I can see your point. For streaming, this is probably something we could address by book-keeping jobs submitted by

Re: [DISCUSS] Change the default restart-strategy to exponential-delay

in the documentation. David On Wed, Nov 15, 2023 at 10:17 PM Rui Fan <1996fan...@gmail.com> wrote: > Hi dear flink users and devs: > > FLIP-364[1] intends to make some improvements to restart-strategy > and discuss updating some of the default values of exponential-delay, > an

RE: How do I source debug the scala in the flink table planner?

. But the Scala breakpoints do not spring. I wonder if it relates to the planner being loaded in a different class loader. Kind regards, David. From: Sergey Nuyanzin Date: Thursday, 2 November 2023 at 19:58 To: dev@flink.apache.org Subject: [EXTERNAL] Re: How do I source debug the scala

How do I source debug the scala in the flink table planner?

– but this is slow and tedious. Ideally I would like to be able to source debug the scala in the flink table planner; any advice would be fab? Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41

Re: Pointers to computational models of Flink CEP

The implementation of Flink CEP was largely based on Efficient Pattern Matching over Event Streams by Jagrati Agrawal, Yanlei Diao, Daniel Gyllstrom, and Neil Immerman from UMass Amherst [1]. [1] https://people.cs.umass.edu/~yanlei/publications/sase-sigmod08.pdf Cheers, David On Tue, Oct 31

RE: flink-sql-connector-jdbc new release

Hi Martijn, Thanks for the link. I suspect I cannot be the release manager, as I do not have the required access, but am happy to help this progress, kind regards, David. From: Martijn Visser Date: Friday, 27 October 2023 at 12:16 To: dev@flink.apache.org Subject: [EXTERNAL] Re: flink

[jira] [Created] (FLINK-33384) MySQL JDBC driver is deprecated

david radley created FLINK-33384: Summary: MySQL JDBC driver is deprecated Key: FLINK-33384 URL: https://issues.apache.org/jira/browse/FLINK-33384 Project: Flink Issue Type: Improvement

RE: flink-sql-connector-jdbc new release

Hi Jing, I just spotted the mailing list that it is a regression – I agree it is a blocker, Kind regards, David. From: David Radley Date: Friday, 27 October 2023 at 10:33 To: dev@flink.apache.org Subject: [EXTERNAL] RE: flink-sql-connector-jdbc new release Hi Jing, thanks are there any

RE: flink-sql-connector-jdbc new release

to try to move it along– could you assign it to me please, Kind regards, David. From: Jingsong Li Date: Friday, 27 October 2023 at 06:54 To: dev@flink.apache.org Subject: [EXTERNAL] Re: flink-sql-connector-jdbc new release Hi David, Thanks for driving this. I think https://issues.apache.org

flink-sql-connector-jdbc new release

regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

Re: [VOTE] Apache Flink Kubernetes Operator Release 1.6.1, release candidate #1

Hi, I downloaded the artifacts. * I did an install of the operator and ran the basic sample * I checked the checksums * Checked the GPG signatures * Ran the UI * Ran a Twistlock scan * I installed 1.6 then did a helm upgrade * I have not managed to do the source build

FW: Maven and java version variables

to resolve another conflict? Kind regards, David. From: David Radley Date: Monday, 23 October 2023 at 12:25 To: dev@flink.apache.org Subject: [EXTERNAL] Maven and java version variables Hi, I have an open pr in the backlog that improves the pom.xml by introducing some Maven variables. The pr is https

RE: Maven and java version variables

Hi Matthias, That sounds reasonable, Kind regards, David From: Matthias Pohl Date: Monday, 23 October 2023 at 16:41 To: dev@flink.apache.org Subject: [EXTERNAL] Re: Maven and java version variables Hi David, The change that caused the conflict in your PR is caused by FLINK-33291 [1]. I

Re: [VOTE] Add JSON encoding to Avro serialization

Looks good to me +1 From: Ryan Skraba Date: Wednesday, 25 October 2023 at 17:19 To: dev@flink.apache.org Subject: [EXTERNAL] [VOTE] Add JSON encoding to Avro serialization Hello! I'm reviewing a new feature of another contributor (Dale Lane) on FLINK-33058 that adds JSON-encoding in addition

RE: Operator 1.6 to Olm

Hi, Fyi with some expert direction from James Busche, I have published the 1.6 OLM and operatorhub.io versions of the Flink operator. When 1.6.1 is out I will do the same again, Kind regards, David. From: Gyula Fóra Date: Tuesday, 10 October 2023 at 13:27 To: dev@flink.apache.org

RE: FLIP-233

Hi Martjin, Yes I am happy to continue to improve the existing Flip. Hi jing, I was looking to continue the discussion and update the Flip content. Are we OK to reopen : FLIP-233? I will update it and the discussion thread there. Kind regards, David. From: Martijn Visser Date: Tuesday

RE: FLIP-233

Thanks Leonard, Hopefully this will be reopened, as we would very much like this capability and want to take over the FLIP, continue the discussion to get a consensus, then implement, Kind regards, David From: Leonard Xu Date: Tuesday, 24 October 2023 at 02:56 To: dev Cc: jd...@amazon.com

FLIP-233

agreement in the discussion thread please, Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

RE: Backport strategy

in case it is misleading? Kind regards, David. From: Martijn Visser Date: Monday, 23 October 2023 at 16:18 To: dev@flink.apache.org Subject: [EXTERNAL] Re: Backport strategy Hi David, The policy is that the current and and previous minor release are supported, and it's documented at https

Backport strategy

of 1.15 1.16 1.17. WDYT? Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

Maven and java version variables

could be extended to include links to this information. I am happy to do that as part of this pr , if needed, if I can be supplied the links. I think this pr should be merged asap, so subsequent pom file changes use the Maven variables. WDYT Kind regards, David. Unless otherwise stated above

Re: Support AWS SDK V2 for Flink's S3 FileSystem

pache/flink/blob/d78d52b27af2550f50b44349d3ec6dc84b966a8a/flink-core/src/main/java/org/apache/flink/core/fs/FileSystem.java#L695 > > [2] > https://github.com/apache/flink/blob/d78d52b27af2550f50b44349d3ec6dc84b966a8a/flink-core/src/main/java/org/apache/flink/core/fs/FileSystem.java#L706

Re: [ANNOUNCE] New Apache Flink Committer - Ron Liu

Congratulations Ron! From: Jark Wu Date: Sunday, 15 October 2023 at 18:57 To: dev Cc: ron9@gmail.com Subject: [EXTERNAL] [ANNOUNCE] New Apache Flink Committer - Ron Liu Hi, everyone On behalf of the PMC, I'm very happy to announce Ron Liu as a new Flink Committer. Ron has been

Re: [DISCUSS] FLIP-375: Built-in cross-platform powerful java profiler on taskmanagers

thread information is nice to drill down into specific parts of the Flink application, e.g. the flame graph lets me ignore the many other tasks running on TM & drill down into just the Source threads, when debugging a Source issue. Kind regards, David On Fri, Oct 13, 2023 at 1:45 AM Rui Fa

RE: FW: RE: [DISCUSS] FLIP-368 Reorganize the exceptions thrown in state interfaces

for them. On balance, as I am risk averse, I would suggest delaying this to v2 as Jing has proposed. This is a cleaner API, is there a demand for this in a dot version? If the community think this is too risk averse, then we could go with 1.19. WDYT? Kind regards, David. From: Jing Ge

  1   2   3   4   5   6   >