Apache Flink connector docs

[kurnoolsaketh]

Summary

Introduce documentation for the official Flink connector. This doc page is adapted from the flink connector repo's README.

closes: ClickHouse/flink-connector-clickhouse#110

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clickhouse-docs	Ready	Preview, Comment	Mar 13, 2026 0:50am
clickhouse-docs-jp	Building	Preview, Comment	Mar 13, 2026 0:50am

3 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
clickhouse-docs-ko	Ignored	Preview	Mar 13, 2026 0:50am
clickhouse-docs-ru	Ignored	Preview	Mar 13, 2026 0:50am
clickhouse-docs-zh	Ignored	Preview	Mar 13, 2026 0:50am

[alexfrancoeur]

The docs look great! A couple of small pieces of feedback, but lgtm overall. I can't wait to get these in there

I reviewed this preview on mobile: https://clickhouse-docs-9zj3bpftf-clickhouse.vercel.app/docs/integrations/apache-flink

• The apache flink icon in the integrations view links to the repo still, we'll need to update in the CMS to link to these docs and make it consistent across the different entry points
• I feel like we should link to the repo explicitly early in the docs with the connector name
• I don't know if we need the "to be filled out later" section for the table api. We could probably just remove until it's added

[BentsiLeviav]

Left a few comments. In addition, can we go over the repo and find relevant locations where Flink is mentioned, and make sure we link them to this page?

Found these locations, but we might have more:

• clickhouse-docs/docs/data-modeling/denormalization.md

  Line 374 in 86362ae

  You may alternatively wish to perform this outside of ClickHouse, prior to insertion, using streaming technologies such as [Apache Flink](https://flink.apache.org/). Alternatively, incremental [materialized views](/guides/developer/cascading-materialized-views) can be used to perform this process as data is inserted.

• clickhouse-docs/docs/best-practices/minimize_optimize_joins.md

  Line 22 in 86362ae

  - You have the capability to shift processing out of ClickHouse into upstream systems like Flink, where real-time enrichment or flattening can be managed.

[kurnoolsaketh]

In addition, can we go over the repo and find relevant locations where Flink is mentioned, and make sure we link them to this page?

@BentsiLeviav yes - i confirmed the locations you identified are the only other mentions of flink in the repo besides the same pages in japanese & other languages. Should I update those as well?

[kurnoolsaketh]

thanks @alexfrancoeur!

• The apache flink icon in the integrations view links to the repo still, we'll need to update in the CMS to link to these docs and make it consistent across the different entry points

i've updated the flink icon link to point to the new docs page 👍

• I feel like we should link to the repo explicitly early in the docs with the connector name

sure will do

• I don't know if we need the "to be filled out later" section for the table api. We could probably just remove until it's added

yup, it's removed now

[kurnoolsaketh]

items 12 and 15 in the doc matrix

[Blargian]

In addition, can we go over the repo and find relevant locations where Flink is mentioned, and make sure we link them to this page?

@BentsiLeviav yes - i confirmed the locations you identified are the only other mentions of flink in the repo besides the same pages in japanese & other languages. Should I update those as well?

@kurnoolsaketh no need to update any of the translations, there is a bot which will open a PR after this gets merged with any updates to translations.

[Blargian]

LGTM, with exception that static/integrations-fallback.json shouldn't be checked in I don't think

addressed