docs: Add MySQL, Postgres, Redshift, and Athena OLAP support documentation #8242
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ation Extends PR #8210 (BigQuery and Snowflake) to include documentation for additional OLAP engines added in recent PRs: - PR #8169: MySQL OLAP interface - PR #8224: Postgres OLAP interface - PR #8232: Redshift OLAP interface - PR #8180: Athena OLAP interface ### Changes to partitioned-models.md - Updated intro text to list all 6 supported OLAP engines (BigQuery, Snowflake, MySQL, Postgres, Redshift, Athena) - Added 4 new complete examples showing partition patterns for each engine: - **MySQL**: Daily partitioning using DATE() function - **Postgres**: Daily partitioning using DATE_TRUNC() - **Redshift**: Monthly partitioning using DATE_TRUNC() - **Athena**: Multi-column partitioning (year, month) - Updated tip box to include all engines ### Changes to custom-apis.md - Renamed section from "Using BigQuery or Snowflake" to "Using Alternative OLAP Engines" - Updated intro to list all 6 supported engines - Added 4 new API examples for MySQL, Postgres, Redshift, and Athena - Expanded cost warning to cover all database/warehouse billing models - Updated "When to use" guidance to be more generic All examples follow the same pattern as PR #8210: use the source connector for querying, then output to DuckDB for fast dashboard performance. Related PRs: #8210, #8169, #8224, #8232, #8180 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
|
not sure how i feel about the long page of examples, but untli we have an example directory integrated in docs, i think its fine. |
ericpgreen2
requested changes
Nov 4, 2025
There was a problem hiding this comment.
I see the Snowflake example doesn't have output: duckdb like the other examples do
There was a problem hiding this comment.
The comment on consistent examples on the Custom APIs page also applies here. E.g., some examples use transactions, others use events.
There was a problem hiding this comment.
i get the reasoning for snowflake not having the YAML, but IMO slightly different SQL should be fine for examples,
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR extends the OLAP engine documentation from PR #8210 (which added BigQuery and Snowflake) to include four additional OLAP engines that were recently added:
Changes
Updated:
partitioned-models.mdSection: "Using Other OLAP Engines for Partition Queries"
DATE()functionDATE_TRUNC()DATE_TRUNC()Example pattern added:
Updated:
custom-apis.mdSection: "Using Alternative OLAP Engines" (renamed from "Using BigQuery or Snowflake")
Example API pattern added:
Documentation Structure
Both files now follow a consistent structure:
Benefits Documented
Related PRs
cc @kanshul
🤖 Generated with Claude Code