Bharath Reddy Gunapati created FLINK-40699:
----------------------------------------------
Summary: Add HTTP sink continue-on-error and optional error/DLQ
handling
Key: FLINK-40699
URL: https://issues.apache.org/jira/browse/FLINK-40699
Project: Flink
Issue Type: Sub-task
Components: Connectors / HTTP
Reporter: Bharath Reddy Gunapati
FLINK-40277 makes fatal / exhausted HTTP sink failures fail the Flink job
(completeExceptionally) instead of silently completing. That is the correct
default for fail-fast, but some jobs may prefer to continue after sink errors
and optionally route failed records / error context to an error sink or DLQ.
This was called out in review on PR #54.
Proposed scope:
- Configurable continue-on-error (or equivalent) so sink failures do not
always kill the job
- Optional path to expose / route failed request content or error context
(e.g. error topic / DLQ), if feasible with AsyncSink semantics
- Document fail-fast vs continue-on-error behavior and compatibility notes
Acceptance criteria:
- Users can opt into continue-on-error without losing fail-fast as default
- Failed writes remain observable (metrics/logs; optional error sink if added)
- Behavior is tested for Table API/SQL and DataStream
- Docs describe the failure modes and migration from silent-complete behavior
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
