Arun Lakshman created FLINK-37811:
-
Summary: Flink Job stuck in suspend state after losing leadership
in Zookeeper HA
Key: FLINK-37811
URL: https://issues.apache.org/jira/browse/FLINK-37811
Project: F
Hi Mayank,
Thanks for the initiative! I think this functionality would be a really
great addition to Flink.
+1 for the proposal.
Thanks,
Yash
On Tue, May 6, 2025 at 9:36 AM Mayank Juneja
wrote:
> Hi Ferenc,
>
> Thanks for your question! We agree that a CONNECTION could logically be a
> catalo
Hi Mayank,
Overall I think the idea of having shared properties (secrets or otherwise)
at the database layer is really interesting/useful. Even outside of the ML
scope.
However, I have a concern:
When I describe a table, I would not like it if all properties did not
appear in the returned results
Mingliang Liu created FLINK-37812:
-
Summary: Fix broken links to Apache Avro in doc and code
Key: FLINK-37812
URL: https://issues.apache.org/jira/browse/FLINK-37812
Project: Flink
Issue Type:
Hi,
I raised a JIRA [1] and PR [2] for this, I can’t see any downsides – only that
it fixes critical vulnerabilities. Unless there are any concerns , could we
merge this please,
Kind regards, David.
[1] https://issues.apache.org/jira/browse/FLINK-37810
[2] https://github.com/apache/flink/pull/2
Hi,
I have amended the design slightly for Flip-518 [1] in 2 respects
* I intend the set the COMMUNITY-REVIEW label for all types for reviews
(not just approves) , as negative and comment reviews should be tracked as they
are often more valuable than approvals.
* I have changed the Flip
david radley created FLINK-37810:
Summary: update log4j to 2.24.3 to fix critical vulnerabilities
Key: FLINK-37810
URL: https://issues.apache.org/jira/browse/FLINK-37810
Project: Flink
Issue
The Apache Flink community is very happy to announce the release of
Apache Flink CDC 3.4.0.
Apache Flink CDC is a distributed data integration tool for real time
data and batch data, bringing the simplicity and elegance of data
integration via YAML to describe the data movement and transformation
Hi all,
We held the 23rd Chi meeting.
* The open PR numbers are down to under 200 now – much more manageable. I
am curious if anyone thinks this is too aggressive.
* We have identified some PRs [2], they are approved and trivial, so in our
opinion should be easy merges. Could a committer
