Bharath Reddy Gunapati created FLINK-40702:
----------------------------------------------
Summary: Unify shared HTTP sink and lookup configuration options
Key: FLINK-40702
URL: https://issues.apache.org/jira/browse/FLINK-40702
Project: Flink
Issue Type: Sub-task
Components: Connectors / HTTP
Environment: HTTP sink and lookup currently duplicate many similar
config keys under
http.sink.* and http.source.lookup.* (timeouts, retries, status-code lists,
TLS, etc.). Review on PR #54 suggested sharing common options, using
withDeprecatedKeys for migration, sharing processing code where possible,
and reorganising docs into common + sink/lookup-specific sections.
Proposed direction (similar to the Kafka table connector):
- Shared / connection-level options for truly common settings
- Keep sink- and lookup-specific keys where behaviour or values may differ
(e.g. different request timeouts for a sink table and a lookup table in
the same job)
- Use withDeprecatedKeys when intentionally renaming current prefixed keys
- Share parsing/validation code for common options
- Docs: common section, then sink- and lookup-specific sections
Same-job different values remain supported because Table options are per
table and DataStream sink/lookup each have their own config.
Acceptance criteria:
- Shared options are identified and documented (common vs sink/lookup)
- Migration path from existing http.sink.* / http.source.lookup.* keys
- Shared parsing/validation where possible without forcing one value for
both sink and lookup in the same job
- Docs reorganised into common + sink/lookup-specific sections
- Unit tests cover shared and role-specific configuration
Reporter: Bharath Reddy Gunapati
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
