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

Bharath Reddy Gunapati closed FLINK-40280.
------------------------------------------
    Resolution: Won't Do

Closing: the documentation this sub-task asked for was delivered with the 
feature changes instead of as a separate PR. Status-code classification, retry 
options and legacy option migration notes: apache/flink-connector-http#54. 
Batch retry semantics and caveats: apache/flink-connector-http#57. OIDC, proxy 
and HTTP version options: apache/flink-connector-http#58 (in review). Fail-fast 
vs continue-on-error documentation belongs to FLINK-40699 together with the 
feature.

> Document HTTP sink retry, error handling, and configuration parity
> ------------------------------------------------------------------
>
>                 Key: FLINK-40280
>                 URL: https://issues.apache.org/jira/browse/FLINK-40280
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Connectors / HTTP
>            Reporter: Bharath Reddy Gunapati
>            Priority: Major
>
> Description:
>   Update HTTP connector documentation to describe the improved sink behavior 
> and how it compares to lookup source behavior.
> Documentation should cover:
>   - Sink status-code classification.
>   - Retry strategy options.
>   - Fail-fast vs continue-on-error behavior, if supported.
>   - Batch retry semantics.
>   - OIDC bearer token support.
>   - Proxy and HTTP version options.
>   - Migration/deprecation notes for existing sink error-code options.
> Acceptance criteria:
>   - Table connector docs include SQL examples.
>   - DataStream connector docs include builder/config examples.
>   - Batch retry caveats are documented.
>   - Deprecated or legacy options are clearly explained.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to