Bharath Reddy Gunapati created FLINK-40700:
----------------------------------------------
Summary: Add typed DataStream configuration for HTTP sink options
Key: FLINK-40700
URL: https://issues.apache.org/jira/browse/FLINK-40700
Project: Flink
Issue Type: Sub-task
Components: Connectors / HTTP
Reporter: Bharath Reddy Gunapati
HTTP sink DataStream configuration today goes through string properties
(HttpSink.builder().setProperty(...)) and HttpSinkConfigFactory.fromDataStream()
maps those keys into typed ConfigOptions one-by-one. That is easy to miss when
new options are added (called out in review on PR #54).
Table API already exposes typed ConfigOptions. DataStream should get a similar
typed surface so users do not rely on string keys for status-code, retry, and
related sink options, and so factory mapping stays in sync.
Proposed scope:
- Add typed setters / builder methods on the DataStream HTTP sink path for the
status-code and retry options (and other sink options as needed)
- Keep setProperty(...) working for compatibility
- Reduce or replace the fragile per-key property-to-config mapping in
HttpSinkConfigFactory.fromDataStream()
- Document the typed DataStream API alongside the existing property keys
Acceptance criteria:
- DataStream users can configure success/retry/ignored codes and retry strategy
without string property keys
- Existing setProperty(...) configurations continue to work
- New typed options do not require a separate forgotten mapping block to take
effect
- Unit tests cover typed DataStream configuration
- Docs show the typed DataStream API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
