[
https://issues.apache.org/jira/browse/FLINK-36400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenzo Nicora updated FLINK-36400:
-----------------------------------
Description:
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
was:
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.
h3. Change required
The error handling behaviour should be ignored on 403 or 404 responses. The
writer should always throw an exception
> 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)
