I have updated the PR for review and also added a new test.
https://github.com/apache/flink-connector-elasticsearch/pull/107
Could you take a look, Ahmed?
Thanks,
On Tue, Jun 11, 2024 at 5:23 AM Ahmed Hamdy wrote:
> Hi Mingliang,
> Yes sounds like a good solution, I am not very familiar with
Hi everyone,
The release candidate #0 (i.e. RC0) for Apache Flink 2.1.0 has been created.
RC0 is for testing purposes only, and we will not vote on it.
RC0 has all the artifacts that we would typically have for a release,
except for the release note and the website pull request for the release
a
+1 (binding)
1. Verified the archives, checksums, and signatures
2. Extracted and inspected the source code for binaries
3. Compiled and tested the source code via mvn install
4. Verified license files / headers
Thanks for preparing the release!
-Max
On Wed, Jul 9, 2025 at 8:38 AM Gyula Fóra
Hi,
I would like to start a conversation about releases for the Flink Connector
Kafka project.
We have recently updated [0] to version 3.9.1 of the Kafka client library,
which fixes a critical CVE [1]. With that in mind, I think it would be prudent
to have a 4.1.0 release as soon as possible t
Gustavo de Morais created FLINK-38073:
-
Summary: Add documentation for the MultiJoin Operator
Key: FLINK-38073
URL: https://issues.apache.org/jira/browse/FLINK-38073
Project: Flink
Issue
Hi Gyula and Tom,
Thanks for your responses. We are not going to work on this in the very short
term , but it is now on our list to do,
Kind regards, David.
From: Gyula Fóra
Date: Tuesday, 8 July 2025 at 17:07
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Flink Kubenetes Operator clien
I am writing on behalf of the Nicolas Fraison.
The voting period is closed. The result will be sent in a separate email.
Thank you all for voting.
On Thu, Jul 3, 2025 at 4:51 PM Őrhidi Mátyás
wrote:
> +1 (binding)
>
> On Thu, Jul 3, 2025 at 3:13 AM Gyula Fóra wrote:
>
> > +1 (binding)
> >
> >
Dear Flink Community,
I am using AsyncDataStream.unorderedWaitWithRetry together with a
RichAsyncFunction to perform asynchronous processing in Flink 1.19. I have
configured a retry strategy using FixedDelayRetryStrategy with a maximum of
3 retries and a delay of 1000 milliseconds.
*Issue:*
When
dalongliu created FLINK-38072:
-
Summary: EventTimeWindowCheckpointingITCase#testSlidingTimeWindow
test failed in cron ci
Key: FLINK-38072
URL: https://issues.apache.org/jira/browse/FLINK-38072
Project: Fl
Hi Honggeun,
It looks like the confusion stems from a documentation issue.
As the code comment explains:
* @param timeout from first invoke to final completion of asynchronous
operation, may include
* multiple retries, and will be reset in case of restart
This means the timeout covers the e
Thank you all!
Closing this vote now.
Gyula
On Wed, Jul 9, 2025 at 10:02 AM Maximilian Michels wrote:
> +1 (binding)
>
> 1. Verified the archives, checksums, and signatures
> 2. Extracted and inspected the source code for binaries
> 3. Compiled and tested the source code via mvn install
> 4. Ve
Hi All!
I'm happy to announce that we have unanimously approved this release.
There are 6 approving votes, 3 of which are binding:
Mate Czagany (non-binding)
Gabor Somogyi (non-binding)
Weiqing Yang (non-binding)
Robert Metzger (binding)
Gyula Fora (binding)
Maximilian Michels (binding)
There a
Thank you for the clarification. I now understand that the timeout() method
is intended to cover all async I/O attempts, including retries. Apologies
for the confusion in my previous message.
If you don’t mind, I’d like to ask one more question to make sure I fully
understand the behavior.
Let’s
kaitian created FLINK-38075:
---
Summary: [Window]Data loss when using ltz time.
Key: FLINK-38075
URL: https://issues.apache.org/jira/browse/FLINK-38075
Project: Flink
Issue Type: Bug
Compon
xiangyu feng created FLINK-38074:
Summary: Release Testing: Verify FLIP-506: Support Reuse Multiple
Table Sinks in Planner
Key: FLINK-38074
URL: https://issues.apache.org/jira/browse/FLINK-38074
Proje
I just have some questions:
1. The current metrics hierarchy shows that the UDF metric group belongs to
the TaskMetricGroup. I think it would be better for the UDF metric group to
belong to the OperatorMetricGroup instead, because a UDF might be used by
multiple operators.
2. What are the naming c
16 matches
Mail list logo