Docs: fix issue with client properties name in Kafka connect sink docs

[chernser]

Description

Updates Kafka Connect Sink documentation where wrongly mentioned that clickhouseSettings should be used for client config (socket_timeout and connection_timeout) while all client settings are passed via jdbcConnectionProperties

Changelog category (leave one):

• Documentation (changelog entry is not required)

Version info

• Merged into: 26.8.1.744 (included in 26.8 and later)

[clickhouse-gh]

Workflow [PR], commit [fd26b6d]

Summary: ✅

---

AI Review

Summary

This PR updates the Kafka Connect Sink docs to move client timeout settings from clickhouseSettings to jdbcConnectionProperties, which is the right direction. I would still block merge, because the page does not yet show a valid jdbcConnectionProperties example and it remains self-contradictory about where socket_timeout belongs.

Findings

⚠️ Majors

• [docs/integrations/connectors/data-ingestion/kafka/kafka-clickhouse-connect-sink.mdx:865] The new example still formats jdbcConnectionProperties incorrectly by comma-separating the parameters, even though the same page documents this field as a ?key=value&key2=value2 query string. The later high-throughput recipe at docs/integrations/connectors/data-ingestion/kafka/kafka-clickhouse-connect-sink.mdx:937 also still routes socket_timeout through clickhouseSettings. As a result, the PR leaves readers with conflicting and partially non-working configuration guidance.
  Suggested fix: change the timeout example to "?socket_timeout=300000&connection_timeout=30000" and add/move jdbcConnectionProperties in the later recipe instead of keeping socket_timeout inside clickhouseSettings.

Final Verdict

Changes requested.

[clickhouse-gh]

jdbcConnectionProperties is documented earlier on this page as a URL query string that starts with ? and joins pairs with &, so this replacement is still not a working example: "?socket_timeout=300000,connection_timeout=30000" keeps the old comma-separated syntax. The page also still has the high-throughput recipe at docs/integrations/connectors/data-ingestion/kafka/kafka-clickhouse-connect-sink.mdx:937 putting socket_timeout into clickhouseSettings, so readers will still see conflicting guidance about where client timeouts belong.

Can we switch this example to "?socket_timeout=300000&connection_timeout=30000" and move the later socket_timeout into jdbcConnectionProperties as well?