Jubin Soni created FLINK-39730:
----------------------------------
Summary: ApplicationExceptionsHandler silently ignores
maxExceptions parameter; ApplicationExceptionsMessageParameters is unreachable
via typed REST client
Key: FLINK-39730
URL: https://issues.apache.org/jira/browse/FLINK-39730
Project: Flink
Issue Type: Bug
Components: Runtime / REST
Reporter: Jubin Soni
Problem:
ApplicationExceptionsHandler does not read the maxExceptions query
parameter from the request. As a result, even after the accessibility
fix in FLINK-39711 (PR #28202), typed Java clients that set
maxExceptions on ApplicationExceptionsMessageParameters will have the
parameter silently discarded by the server.
Root cause (discovered during FLINK-39711):
1. ApplicationExceptionsHeaders is typed on ApplicationMessageParameters
(the parent class), not on ApplicationExceptionsMessageParameters.
This means ApplicationExceptionsMessageParameters is orphaned
scaffolding — it is never wired into the handler.
2. ApplicationExceptionsHandler does not call
HandlerRequestUtils.getFromOptionalValue() for maxExceptions,
unlike JobExceptionsHandler which already reads the parameter
correctly.
This gap was introduced in FLINK-38977 when
ApplicationExceptionsMessageParameters was added but the handler
wiring was not completed.
Expected behavior:
ApplicationExceptionsHandler should read maxExceptions from the
request and bound the response size, consistent with the behavior
of JobExceptionsHandler.
Related: FLINK-39711, FLINK-38977, [PR
#28202|https://github.com/apache/flink/pull/28202]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
