Skip to content

Document the dbt connector for QuestDB Enterprise - #596

Open
kafka1991 wants to merge 6 commits into
mainfrom
docs/dbt-enterprise-connector
Open

kafka1991 wants to merge 6 commits into
mainfrom
docs/dbt-enterprise-connector

Conversation

@kafka1991

Copy link
Copy Markdown
Contributor

Adds the dbt connector under Connectors, with an Enterprise notice and installation instructions for the release archive.

The guide covers the bundled trades project, using existing tables as sources, connection and model settings, incremental updates, materialized views, snapshots, and operational limitations.

Also updates the Java examples source from master to main, fixing the missing manifest encountered during the site build.

Validation: production documentation build passed; both the bundled project and the documented existing-table example were built twice against QuestDB. The rendered Enterprise notice and release packaging were also checked.

@github-actions

github-actions Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

🚀 Build success!

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

Commit SHA: efb22ba

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

@kafka1991 kafka1991 self-assigned this Oct 23, 2026
@kafka1991 kafka1991 added the READY The PR is ready for final review and approval label Oct 23, 2026
mtopolnik and others added 3 commits October 23, 2026 16:59
…uide

The existing-table example builds candles as a materialized view that
QuestDB refreshes as trades arrive, plus a note on at-least-once delivery
and deduplication keys. A new "Keep prefix mode" subsection shows how to
read ingested tables by writing them with a prefix. The install step
states dbt Core 1.x and explains the "Could not determine latest version"
line from dbt --version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The materialized and live views section points to the dbt connector for
defining those views as tested, version-controlled models over the
ingested tables.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
threads: 4
```

Add `tls: true` for a TLS endpoint. The profile name, `questdb_trades`, matches

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I would place this directly into the yaml, as on enterprise TLS is the default? WHat we can add is how to accept a self signed certificate if you are in a dev environment

@javier javier left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I would add a few more things. Please see comments


### 2. Configure the example

The release includes a complete project with sample trades. From the extracted

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I find this page a bit weak. It only shows how to configure a matview, but it doesn't show how to create a table, which is in the release files, but not here in the docs. At the very least I would show the file at https://github.com/questdb/questdb-dbt-connector/blob/initial_connector/examples/trades/models/marts/trades.sql, but ideally I would show more examples also of different type of materialized views.

It would also be interesting to write if regular views and/or live views are supported, and how to transform data via sql, which is one of the main things in dbt

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

Labels

READY The PR is ready for final review and approval

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants