Skip to content

docs(kafka): document lookup enrichment - #639

Draft
jerrinot wants to merge 4 commits into
mainfrom
jh_kafka_enrichment
Draft

jerrinot wants to merge 4 commits into
mainfrom
jh_kafka_enrichment

Conversation

@jerrinot

@jerrinot jerrinot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Kafka events often carry only an ID (such as instrument_id) while the readable attribute (such as ticker) lives in a QuestDB reference table. Connector 0.26 can look that attribute up and write it into every row, so queries no longer need a join.

This PR documents the feature on the Kafka connector page:

  • Lookup enrichment: a minimal config, an example of the resulting row, how key and value columns are named and typed, and what the query connection needs.
  • Enrichment behavior: what to expect for unmapped keys, redelivery and dedup, startup and reload failures, query timeouts vs. max.poll.interval.ms, and column name clashes.
  • Configuration reference: the four enrichment.* options.
  • The HTTP transport section notes that enrichment requires ws/wss.

@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

🚀 Build success!

Latest successful preview: https://preview-639--questdb-documentation.netlify.app/docs/

Commit SHA: a74c682

📦 Build generates a preview & updates the link on each commit.

- Lookup reloads run in the background, also while idle; only the
  first load blocks a task. enrichment.refresh.ms is at least 100.
- The supported key and value column types, the cast for others, and
  how a record field matches the key column by value.
- What the connector logs when the enriched column stays null.
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