You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Lorenzo Nicora (Jira)" <ji...@apache.org> on 2024/10/28 10:24:00 UTC

[jira] [Closed] (FLINK-36400) 403 and 404 responses should be fatal

     [ https://issues.apache.org/jira/browse/FLINK-36400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lorenzo Nicora closed FLINK-36400.
----------------------------------
    Release Note: Fixed as part of changing error handling behavior
      Resolution: Fixed

> 403 and 404 responses should be fatal
> -------------------------------------
>
>                 Key: FLINK-36400
>                 URL: https://issues.apache.org/jira/browse/FLINK-36400
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Connectors / Prometheus
>            Reporter: Lorenzo Nicora
>            Priority: Major
>
> h3. The issue
> If the endpoint requires authentication and the connector is not configured with correct authentication and credentials, the endpoint throws 403. This should be considered fatal. The connector should never continue.
> Similarly, if the endpoint URL path is misconfigured, Prometheus may respond with a 404. This should also be considered fatal.
> With the current behaviour, every 4xx exception (except 429) is considered "non-retriable" as by specs, and the connector discard and continue. But 403 and 404 are usually caused by a misconfiguration, and the connector should fail.
> h3. Change required
> The error handling behaviour should be ignored on 403 or 404 responses. The writer should always throw an exception 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)