[jira] [Created] (FLINK-34452) Release Testing: Verify FLINK-15959 Add min number of slots configuration to limit total number of slots

2024-02-16 Thread xiangyu feng (Jira)
xiangyu feng created FLINK-34452: Summary: Release Testing: Verify FLINK-15959 Add min number of slots configuration to limit total number of slots Key: FLINK-34452 URL:

Flink's treatment to "hadoop" and "yarn" configuration overrides seems unintuitive

2024-02-16 Thread Venkatakrishnan Sowrirajan
Hi Flink devs, Flink supports overriding "hadoop" and "yarn" configuration. As part of the override mechanism, users have to prefix `hadoop` configs with " flink.hadoop." and the prefix will be removed, while with `yarn` configs users have to prefix it with "flink.yarn." but "flink." only is

[jira] [Created] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

2024-02-16 Thread Alex Hoffer (Jira)
Alex Hoffer created FLINK-34451: --- Summary: [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach Key: FLINK-34451 URL: https://issues.apache.org/jira/browse/FLINK-34451

Re: FLINK-21672

2024-02-16 Thread Martijn Visser
Well I wouldn't be too comfortable with merging a change about how Flink works on different JDKs at this stage, especially since we already have to test for 4 different JDKs at this point. On Fri, Feb 16, 2024 at 5:00 PM Gyula Fóra wrote: > > Depending on the scope of this change, it may not be

Re: FLINK-21672

2024-02-16 Thread Gyula Fóra
Depending on the scope of this change, it may not be considered a feature right Martijn? If it's a test improvement, can it still be part of the release? Gyula On Fri, Feb 16, 2024 at 4:45 PM Martijn Visser wrote: > Hi David, > > Happy to assign it to you. It can't be merged for Flink 1.19

Re: FLINK-21672

2024-02-16 Thread Martijn Visser
Hi David, Happy to assign it to you. It can't be merged for Flink 1.19 anymore though: feature freeze has started for that one, as announced previously on the mailing list. Best regards, Martijn On Fri, Feb 16, 2024 at 4:32 PM David Radley wrote: > > Hi, > I see

FLINK-21672

2024-02-16 Thread David Radley
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

[jira] [Created] (FLINK-34450) TwoInputStreamTaskTest.testWatermarkAndWatermarkStatusForwarding failed

2024-02-16 Thread Matthias Pohl (Jira)
Matthias Pohl created FLINK-34450: - Summary: TwoInputStreamTaskTest.testWatermarkAndWatermarkStatusForwarding failed Key: FLINK-34450 URL: https://issues.apache.org/jira/browse/FLINK-34450 Project:

Re: [VOTE] Release flink-connector-parent, release candidate #1

2024-02-16 Thread Etienne Chauchot
Hi, OK. I thought that not changing the artifact did not require a new RC as the release doc says that "some changes" do not require RC invalidation (it is my first release :) ). Thanks. I'll cancel this release vote and start a RC2 vote. Regarding the empty tool directory, as mentioned

[jira] [Created] (FLINK-34449) Flink build took too long

2024-02-16 Thread Matthias Pohl (Jira)
Matthias Pohl created FLINK-34449: - Summary: Flink build took too long Key: FLINK-34449 URL: https://issues.apache.org/jira/browse/FLINK-34449 Project: Flink Issue Type: Bug