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

he 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. > > Best regar

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,

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

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,

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

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

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

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

the 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]

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

, 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? >Kind regar

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

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

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 > Subject:

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

o deserialize the DynamicMessage before > > > > converting > > > > > > it to RowData using a DynamicMessageToRowDataConverter class. For > > the > > > > > other > > > > > > aspects, I would need to start from scratch for the encoder.

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

Hi Han, Thanks for getting back to me. I am curious about the valid characters in a model name – I assume any characters are valid as it is a quoted string in SQL. So $ could be in the model name. I would think that the model would be determined then the model is deployed, ( there could be

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

: Friday, 22 March 2024 at 13:05 To: dev@flink.apache.org Subject: [EXTERNAL] Re: [DISCUSS] FLIP-XXX Apicurio-avro format Hi David, Thanks a lot for clarification. Sounds good to me. Regards, Jeyhun On Fri, Mar 22, 2024 at 10:54 AM David Radley wrote: > Hi Jeyhun, > Thanks for your feedback.

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

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 resource. Versions are notoriously difficult to add later; I don’t think we want to

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

, can you elaborate more on message consistency in the context of schema evolution? Regards, Jeyhun On Wed, Mar 20, 2024 at 4:34 PM David Radley wrote: > Thank you very much for your feedback Mark. I have made the changes in the > latest google document. On reflection I agree wi

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

avro.globalid-placement having a default value of > HEADER . Should we try all three, or fail if this config param has a wrong > value? > > Other considerations > The implementation does not use the Apicurio deser libraries, > Please can we refer to them as SerDes; this is th

[DISCUSS] FLIP-XXX Apicurio-avro format

Hi, As per the FLIP process I would like to raise a FLIP, but do not have authority, so have created a google doc for the Flip to introduce a new Apicurio Avro format. The document is https://docs.google.com/document/d/14LWZPVFQ7F9mryJPdKXb4l32n7B0iWYkcOdEd1xTC7w/edit?usp=sharing I have

RE: Additional metadata available for Kafka serdes

? Happy to test things out, provide feedback. I'm not working on an Apicurio format myself, but the use case is very similar. Thanks, Balint On Thu, Mar 14, 2024 at 12:41 PM David Radley wrote: > Hi , > I am currently prototyping an Avro Apicurio format that I hope to raise as > a FLIP

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: >

Re: Additional metadata available for Kafka serdes

Hi , I am currently prototyping an Avro Apicurio format that I hope to raise as a FLIP very soon (hopefully by early next week). In my prototyping , I am passing through the Kafka headers content as a map to the DeserializationSchema and have extended the SerializationSchema to pass back

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

Hi Kevin, Some thoughts on this. I suggested an Apicurio registry format in the dev list, and was advised to raise a FLIP for this, I suggest the same would apply here (or the alternative to FLIPs if you cannot raise one). I am prototyping an Avro Apicurio format, prior to raising the Flip,

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

Hi, I see https://issues.apache.org/jira/browse/FLINK-21672 has been open for a while. We at IBM are building Flink with the latest v11 Semeru JDK (https://developer.ibm.com/languages/java/semeru-runtimes/). Flink fails to build with skipTests. It fails because sun.management.VMManagement

RE: Issues running with Flink 1.20-SNAPSHOT

? Best regards, Martijn On Fri, Feb 9, 2024 at 4:43 PM David Radley wrote: > > Hello, > I am git cloned the latest flink to a new folder. I emptied my .m2 folder for > Flink then ran. > > mvn clean > > and see error > > [ERROR] Failed to execute goal on

Issues running with Flink 1.20-SNAPSHOT

Hello, I am git cloned the latest flink to a new folder. I emptied my .m2 folder for Flink then ran. mvn clean and see error [ERROR] Failed to execute goal on project flink-dist_2.12: Could not resolve dependencies for project org.apache.flink:flink-dist_2.12:jar:1.20-SNAPSHOT: The following

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

ml#CheckingSignatures On Thu, Feb 8, 2024 at 12:38 PM David Radley wrote: > Hi, > I was looking more at the asc files. I imported the keys and tried. > > > gpg --verify flink-connector-jdbc-3.1.2-1.16.jar.asc > > gpg: no signed data > > gpg: can't hash datafile: No data

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

1.17.x, 1.18.x) Please let me know whether this answers your question or not [1] https://lists.apache.org/thread/rlk5kp2vxgkmbxmq4wnco885q5vv9rtp [2] https://repository.apache.org/content/repositories/orgapacheflink-1706/ On Wed, Feb 7, 2024 at 12:18 PM David Radley wrote: > Hi , > I ha

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

Hi , I had a question on Flink jdbc connector new release. I notice for the last release we have https://mvnrepository.com/artifact/org.apache.flink/flink-connector-jdbc/3.1.1-1.16 https://mvnrepository.com/artifact/org.apache.flink/flink-connector-jdbc/3.1.1-1.17 It seems that the 2 jars above

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

, Feb 2, 2024 at 5:42 PM David Radley wrote: > 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< > https://nightlies.apache.org/flink/flink-docs-master/api/java/org/a

RE: Flink JDBC connector release

David Radley wrote: > 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< > https://nightlies.apache.org/flink/flink-docs-master/api/java/org/apache/flink/table

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

Hi, [x] -1, Do not approve the release (please provide specific comments) I wanted clarifications on our thinking around the following. In the source code https://github.com/apache/flink-connector-jdbc/releases/tag/v3.1.2-rc2 * This release introduces (I assume experimental, like Flink’s

[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: [VOTE] Release flink-connector-jdbc, release candidate #1

Hi , I am working on FLINK-33365. I am making good progress; thanks Sergey for your fabulous feedback. A lot of the query cases are now working with the latest fix but not all. I think it is pragmatic to revert the lookup join predicate pushdown support, so we can release a functional JDBC

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 as a

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

Hi, When I build the JDBC connector locally on my M1 Mac with a mvn clean install, I get the following errors: in (XaFacadeImpl.java:75) [ERROR] Errors: [ERROR] DerbyExactlyOnceSinkE2eTest.testInsert » JobExecution Job execution failed. [ERROR] MySqlExactlyOnceSinkE2eTest »

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: [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

sted in knowing how the avro-apicurio and > avro-confluent formats would differ! Outside of configuration > options, are there different features? Would the two schema registry > formats have a lot of common base that we could take advantage of? > > All my best, Ryan > > On

RE: Apicurio Avro format proposal

:46 PM David Radley wrote: > > Hi, > I would like to propose a new Apicurio Avro format. > The Apicurio Avro Schema Registry (avro-apicurio) format would allow you to > read records that were serialized by the > io.apicurio.registry.serde.avro.AvroKafkaSerializer and to write r

Apicurio Avro format proposal

Hi, I would like to propose a new Apicurio Avro format. The Apicurio Avro Schema Registry (avro-apicurio) format would allow you to read records that were serialized by the io.apicurio.registry.serde.avro.AvroKafkaSerializer and to write records that can in turn be read by the

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

) set breakpoints both in java and scala and debug... Or what is the issue with this? On Thu, Nov 2, 2023 at 6:59 PM David Radley wrote: > Hi, > I am working on issue https://issues.apache.org/jira/browse/FLINK-33365 > which has been marked as critical and a blocker for the nex

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

Hi, I am working on issue https://issues.apache.org/jira/browse/FLINK-33365 which has been marked as critical and a blocker for the next release of the jdbc connector. I can recreate an issue locally using code I built from source, so I can add in println’s which are coming out – but this is

RE: flink-sql-connector-jdbc new release

-sql-connector-jdbc new release Hi David, The release process for connector is documented at https://cwiki.apache.org/confluence/display/FLINK/Creating+a+flink-connector+release Best regards, Martijn On Fri, Oct 27, 2023 at 12:00 PM David Radley wrote: > > Hi Jing, > I just spotted th

[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

/jira/browse/FLINK-33365 should be a blocker. Best, Jingsong On Thu, Oct 26, 2023 at 11:43 PM David Radley wrote: > > Hi, > I propose that we do a 3.2 release of flink-sql-connector-jdbc so that there > is a version matching 1.18 that includes the new dialects. I am happy to > d

flink-sql-connector-jdbc new release

Hi, I propose that we do a 3.2 release of flink-sql-connector-jdbc so that there is a version matching 1.18 that includes the new dialects. I am happy to drive this, some pointers to documentation on the process and the approach to testing the various dialects would be great, Kind

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

eck [1] in the section Verify Java and Maven Version. Thanks! > > > > Best regards, > > Jing > > > > > > [1] > > > https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release > > > > On Mon, Oct 23, 2023 at 1:25 PM David Radley

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

Subject: [EXTERNAL] Re: Operator 1.6 to Olm That would be great David, thank you! Gyula On Tue, 10 Oct 2023 at 14:13, David Radley wrote: > Hi, > I notice that the latest version in olm of the operator is 1.5. I plan to > run the scripts to publish the 1.6 Flink operator to olm, &g

RE: FLIP-233

; > On Tue, Oct 24, 2023 at 10:55 AM David Radley > wrote: > > > 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

RE: FLIP-233

://lists.apache.org/thread/cd60ln4pjgml7sv4kh23o1fohcfwvjcz > 2023年10月24日 上午12:41，David Radley 写道： > > Hi, > I notice > https://cwiki.apache.org/confluence/display/FLINK/FLIP-233%3A+Introduce+HTTP+Connector > has been abandoned , due to lack of capacity. I work f

FLIP-233

Hi, I notice https://cwiki.apache.org/confluence/display/FLINK/FLIP-233%3A+Introduce+HTTP+Connector has been abandoned , due to lack of capacity. I work for IBM and my team is interested in helping to get this connector contributed into Flink. Can we open this Flip again and we can look to get

RE: Backport strategy

regards, Martijn On Mon, Oct 23, 2023 at 4:16 PM David Radley wrote: > > Hi, > I am relatively new to the Flink community. I notice that critical fixes are > backported to previous versions. Do we have a documented backport strategy > and set of principles? > > The reason I as

Backport strategy

Hi, I am relatively new to the Flink community. I notice that critical fixes are backported to previous versions. Do we have a documented backport strategy and set of principles? The reason I ask is that we recently moved removed the Kafka connector from the core repository, so the Kafka

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://github.com/apache/flink/pull/23469 It has been reviewed but not merged. In the meantime another pom change has been added that caused a conflict. I have amended the code in my

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: FW: RE: [DISCUSS] FLIP-368 Reorganize the exceptions thrown in state interfaces

akelly > > On Fri, Oct 13, 2023 at 3:03 PM Yuan Mei wrote: > > > > +1 for the proposal > > > > But "Since the signature of the public state API has been changed", I was > > wondering whether this would be more fittable in Flink 2.0, instead of > 1.19?

[jira] [Created] (FLINK-33269) light and dark scss files do not have apache licenses at the top.

david radley created FLINK-33269: Summary: light and dark scss files do not have apache licenses at the top. Key: FLINK-33269 URL: https://issues.apache.org/jira/browse/FLINK-33269 Project: Flink

RE: FW: RE: Close orphaned/stale PRs

cally adding a label in case their PR isn't mergeable for the situations that are displayed in situation 1 When that's done, we can see what the effect is on the PRs queue. Best regards, Martijn On Wed, Oct 4, 2023 at 5:13 PM David Radley wrote: > > Hi Ryan, > > I agree that good communic

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

-compatibility-guarantees On Tue, Oct 10, 2023 at 6:19 PM David Radley wrote: > > Hi, > I notice > https://nightlies.apache.org/flink/flink-docs-master/api/java/org/apache/flink/api/common/state/ValueState.html > is an external API. I am concerned that this change will break existing >

Operator 1.6 to Olm

Hi, I notice that the latest version in olm of the operator is 1.5. I plan to run the scripts to publish the 1.6 Flink operator to olm, Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO

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

a new class ValueState2– that is used internally with the cleaned up Exceptions, but still expose the old class and Exceptions for existing external applications. I guess new applications could use the new ValueState2 . What do you think? Kind regards, David. From: David Radley Date

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

Hi , The argument seems to be that the errors cannot be acted on so should be runtime exceptions. I want to confirm that none of these errors could / should be retriable. If there is a possibility that the state is available at some time later then I assume a checked retriable Exception would

RE: [ANNOUNCE] Release 1.18.0, release candidate #0

on connector statuses. There’s already work being done to fix the Flink Kafka connector. Any Flink connector comes after the new minor version, similar to how it has been for all other connectors with Flink 1.17. Best regards, Martijn Visser Op do 5 okt 2023 om 11:33 schreef David Radley >

RE: [ANNOUNCE] Release 1.18.0, release candidate #0

, those issues might need more time, we should move forward with the Flink release without waiting for them. WDYT? Best regards, Jing On Wed, Oct 4, 2023 at 6:15 PM David Radley wrote: > Hi , > As release 1.18 removes the kafka connector from the core Flink > repository, I assume we

RE: [ANNOUNCE] Release 1.18.0, release candidate #0

Hi , As release 1.18 removes the kafka connector from the core Flink repository, I assume we will wait until the kafka connector nightly build issues https://issues.apache.org/jira/browse/FLINK-33104 and https://issues.apache.org/jira/browse/FLINK-33017 are resolved before releasing 1.18?

Kafka Connector

Hi, I was looking at the pr backlog in the Flink repository and realise that there are 51 hits on the search https://github.com/apache/flink/pulls?q=is%3Apr+is%3Aopen+kafka-connector. And 25 hits on

RE: FW: RE: Close orphaned/stale PRs

ainstorming for ideas, and get the virtual circle that David mentioned! All my best, Ryan On Wed, Oct 4, 2023 at 12:03 PM David Radley wrote: > > Hi, > To add I agree with Martijn’s insights; I think we are saying similar things. > To progress agreed upon work, and not blanket close al

FW: RE: Close orphaned/stale PRs

Hi, To add I agree with Martijn’s insights; I think we are saying similar things. To progress agreed upon work, and not blanket close all stale prs, Kind regards, David. From: David Radley Date: Wednesday, 4 October 2023 at 10:59 To: dev@flink.apache.org Subject: [EXTERNAL] RE: Close

RE: Close orphaned/stale PRs

Hi , I agree Venkata this issue is bigger than closing out stale prs. We can see that issues are being raised at a rate way above the resolution time.

RE: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

Hi, I agree this is a standardising, simplifying change for read, simplifying programmatically authoring the config file as well. As you know the mapping for the old config form to the new form, could we write a migration tool, that would convert the old config files to the new format, with

Rest ports

Hello, I notice: *the web UI listens on port 8081, * The default port for that Flink listens on for rest calls is 8081. * Specifying rest.port in the configuration changes the port for both listeners. We would like the 2 ports to be different so they can be secured differently,

FLINK-33159

Hi, I re-opened https://issues.apache.org/jira/browse/FLINK-33159 . After it closed as will not fix- l hopefully the words I have added reassure you that this is a benign change – I intended this to just clean the build file by using variables. I wanted to check this is ok with the community,

[jira] [Created] (FLINK-33165) Flink UI stack trace popup continually displayed when a job is deleted

david radley created FLINK-33165: Summary: Flink UI stack trace popup continually displayed when a job is deleted Key: FLINK-33165 URL: https://issues.apache.org/jira/browse/FLINK-33165 Project

  1   2   >