Skip to content

[client] Add validation for client.scanner.log.max-poll-records and client.connect-timeout#3069

Open
Prajwal-banakar wants to merge 1 commit intoapache:mainfrom
Prajwal-banakar:client-Add-validation
Open

[client] Add validation for client.scanner.log.max-poll-records and client.connect-timeout#3069
Prajwal-banakar wants to merge 1 commit intoapache:mainfrom
Prajwal-banakar:client-Add-validation

Conversation

@Prajwal-banakar
Copy link
Copy Markdown
Contributor

Purpose

Linked issue: close #3068

Add client config validation for client.scanner.log.max-poll-records and client.connect-timeout during FlussConnection initialization. Setting either of these to 0 or negative makes no practical sense — poll() would return nothing and TCP connect would time out immediately.

Brief change log

  • Added validateClientConfigs() in FlussConfigUtils covering client.scanner.log.max-poll-records (must be > 0) and client.connect-timeout (must be > 0)
  • Called validateClientConfigs() in FlussConnection constructor
  • Added unit tests in FlussConfigUtilsTest

Tests

Existing FlussConfigUtilsTest extended with testValidateClientConfigs() covering default validity and each invalid case.

API and Format

NO

Documentation

NO

@Prajwal-banakar
Copy link
Copy Markdown
Contributor Author

cc @fresh-borzoni @LiebingYu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[client] Add validation for client.scanner.log.max-poll-records and client.connect-timeout config options

1 participant