Aleksandr Savonin created FLINK-39711:
-----------------------------------------
Summary: Allow setting maxExceptions on
JobExceptionsMessageParameters / ApplicationExceptionsMessageParameters
Key: FLINK-39711
URL: https://issues.apache.org/jira/browse/FLINK-39711
Project: Flink
Issue Type: Improvement
Components: Runtime / REST
Reporter: Aleksandr Savonin
Problem:
The REST endpoint \{{GET /jobs/:jobid/exceptions}} accepts an optional
\{{maxExceptions}} query parameter that bounds the size of the response, but
Java clients of Flink's typed REST API cannot set it.
As a result, downstream Java clients (for example
\{{apache/flink-kubernetes-operator}}) fetch the *full* existing job exception
history on every observation tick. For long-running jobs with large exception
histories this is wasteful in terms of network bytes, JobManager-side
serialization, and operator JVM memory.
Same gap exists for ApplicationExceptionsMessageParameters.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
