Skip to content

Conversation

@jia17
Copy link
Contributor

@jia17 jia17 commented Apr 25, 2025

fix: #9226

Purpose of this pull request

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

Hisoka-X
Hisoka-X previously approved these changes Apr 25, 2025
@Hisoka-X
Copy link
Member

Thanks @jia17

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR makes sink parameters optional for the DataHub connector by moving the TIMEOUT and RETRY_TIMES options from required to optional and assigning them default values.

  • Updated DataHubSinkFactory option rules to mark TIMEOUT and RETRY_TIMES as optional
  • Set default values for TIMEOUT (3000) and RETRY_TIMES (3) in DataHubSinkOptions
  • Adjusted both English and Chinese documentation to reflect the new optional nature and default values

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
seatunnel-connectors-v2/connector-datahub/sink/DataHubSinkFactory.java Adjusted option rule for DataHub connector to mark TIMEOUT and RETRY_TIMES as optional
seatunnel-connectors-v2/connector-datahub/config/DataHubSinkOptions.java Updated default values for TIMEOUT and RETRY_TIMES
docs/zh/connector-v2/sink/Datahub.md Updated documentation to reflect optional TIMEOUT and RETRY_TIMES with default values
docs/en/connector-v2/sink/Datahub.md Updated documentation to reflect optional TIMEOUT and RETRY_TIMES with default values

@corgy-w
Copy link
Contributor

corgy-w commented Apr 26, 2025

Please try ci again

@hailin0 hailin0 merged commit 7418fae into apache:dev Apr 27, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature][Connector-V2] Make some parameters optional to align with DataHub implementation

4 participants