[ https://issues.apache.org/jira/browse/FLINK-32198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727746#comment-17727746 ]
Panagiotis Garefalakis commented on FLINK-32198: ------------------------------------------------ This is a breaking change so will have to wait for Flink 2.0 > Enforce single maxExceptions query parameter > -------------------------------------------- > > Key: FLINK-32198 > URL: https://issues.apache.org/jira/browse/FLINK-32198 > Project: Flink > Issue Type: Bug > Components: Runtime / REST > Reporter: Panagiotis Garefalakis > Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > > While working on FLINK-31894 I realized that `UpperLimitExceptionParameter` > allows multiple values to be collected as a comma separated list even though > JobExceptionsHandler is only using the first one > [https://github.com/apache/flink/blob/1293958652053c0d163fde28e8dfefb5ee8f6101/flink-runtime/src/main/java/org/apache/flink/runtime/rest/handler/job/JobExceptionsHandler.java#L101-L104] > A better approach would be to deny multiple `maxExceptions` params and let > the users know. > -- This message was sent by Atlassian Jira (v8.20.10#820010)