[
https://issues.apache.org/jira/browse/FLINK-40276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharath Reddy Gunapati closed FLINK-40276.
------------------------------------------
Resolution: Invalid
> Add HTTP sink response classification and retry support
> -------------------------------------------------------
>
> Key: FLINK-40276
> URL: https://issues.apache.org/jira/browse/FLINK-40276
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / HTTP
> Reporter: Bharath Reddy Gunapati
> Priority: Major
>
> The HTTP lookup source supports configurable success codes, retry codes,
> ignored response codes, and retry strategies. The HTTP sink currently detects
> failures but does not retry failed entries in HttpSinkWriter.
> Add sink-side response classification and retry behavior aligned with lookup
> source semantics.
> Proposed options:
> - http.sink.success-codes, default 2XX
> - http.sink.retry-codes, default 500,503,504
> - http.sink.ignored-response-codes, default empty
> - http.sink.retry-strategy.type
> - http.sink.retry-strategy.fixed-delay.delay
> - http.sink.retry-strategy.exponential-delay.initial-backoff
> - http.sink.retry-strategy.exponential-delay.max-backoff
> - http.sink.retry-strategy.exponential-delay.backoff-multiplier
> Acceptance criteria:
> - Sink retries transport failures and configured retryable HTTP status
> codes.
> - Sink does not retry configured ignored response codes.
> - Retry behavior is available for Table API/SQL and DataStream API.
> - Retry exhaustion behavior is deterministic and tested.
> - Existing tests are updated and new tests cover success, retryable
> failure, fatal failure, and ignored response codes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)