Maciej Bryński created FLINK-33163:
--
Summary: Support Java 21 (LTS)
Key: FLINK-33163
URL: https://issues.apache.org/jira/browse/FLINK-33163
Project: Flink
Issue Type: Bug
Reporte
xiaogang zhou created FLINK-33162:
-
Summary: seperate the executor in
DefaultDispatcherResourceManagerComponentFactory for MetricFetcher and
webMonitorEndpoint
Key: FLINK-33162
URL: https://issues.apache.org/jira
Zakelly Lan created FLINK-33161:
---
Summary: [benchmark] Java17 profile for benchmarks
Key: FLINK-33161
URL: https://issues.apache.org/jira/browse/FLINK-33161
Project: Flink
Issue Type: Bug
dizhou cao created FLINK-33160:
--
Summary: Print the remote address when an exception occurs in the
PartitionRequestQueue
Key: FLINK-33160
URL: https://issues.apache.org/jira/browse/FLINK-33160
Project: F
Hi Martijn,
Agree with your point that closing a PR without any review feedback even
after 'X' days is discouraging to a new contributor. I understand that this
is a capacity problem. Capacity problem cannot be solved by this proposal
and it is beyond the scope of this proposal.
Regarding your ea
david radley created FLINK-33159:
Summary: Use the variables for java and Maven version checks in
the pom file
Key: FLINK-33159
URL: https://issues.apache.org/jira/browse/FLINK-33159
Project: Flink
Dawid Wysakowicz created FLINK-33158:
Summary: Cryptic exception when there is a StreamExecSort in
JsonPlan
Key: FLINK-33158
URL: https://issues.apache.org/jira/browse/FLINK-33158
Project: Flink
Hi all,
We would like to revive the discussion and provide a quick update on
the recent work of the FLIP. We have implemented a POC[1], run cases
in the flink-benchmarks[2] against the POC, and verified that many of
the operators in the benchmark will enable object-reuse without code
changes, whil
Maomao Min created FLINK-33157:
--
Summary: Support AWS SDK V2 for Flink's S3 FileSystem
Key: FLINK-33157
URL: https://issues.apache.org/jira/browse/FLINK-33157
Project: Flink
Issue Type: Improvem
