Skip to content

Remove max_workers and alive_nodes_checking_frequency from async replication config#2044

Open
mpartipilo wants to merge 2 commits into
mainfrom
remove-deprecated-async-replication-fields
Open

Remove max_workers and alive_nodes_checking_frequency from async replication config#2044
mpartipilo wants to merge 2 commits into
mainfrom
remove-deprecated-async-replication-fields

Conversation

@mpartipilo
Copy link
Copy Markdown
Contributor

Summary

  • Removes max_workers and alive_nodes_checking_frequency from Configure.Replication.async_config(), Reconfigure.Replication.async_config(), the Pydantic wire models, the read-side dataclass, and the response parser.
  • Both fields have been no-ops on the server since Weaviate 1.37.3 — the server silently ignores whatever value the client sends.
  • Integration and unit tests updated to use propagation_concurrency and hashtree_height for round-trip assertions (fields that do survive the server round-trip).

Breaking change

Existing code that passes max_workers=... or alive_nodes_checking_frequency=... will raise a TypeError at runtime after upgrading. No behavioral regression — those values were already being ignored by the server.

Related

  • Server change: Weaviate 1.37.3 made these fields no-ops.
  • Same removal applied to TypeScript and C# clients in their respective empty_default_vector_index branches.

🤖 Generated with Claude Code

mpartipilo and others added 2 commits May 21, 2026 22:17
…ication config

Both fields are no-ops on servers >= 1.37.3 (the server silently ignores
them), making round-trip assertions unreliable. Remove from the Pydantic
create/update models, the read dataclass, both factory methods
(Configure/Reconfigure.Replication.async_config), and the parser.

Integration and unit tests are updated to use propagation_concurrency
and hashtree_height, which do round-trip correctly on all supported
server versions.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…moval

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown

@orca-security-eu orca-security-eu Bot left a comment

Choose a reason for hiding this comment

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

Orca Security Scan Summary

Status Check Issues by priority
Passed Passed Infrastructure as Code high 0   medium 0   low 0   info 0 View in Orca
Passed Passed SAST high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Secrets high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Vulnerabilities high 0   medium 0   low 0   info 0 View in Orca

@mpartipilo mpartipilo marked this pull request as ready for review May 21, 2026 21:09
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.

1 participant