refactor(parquet): use parquet and duckdb instead of postgresql#121
Draft
bolinocroustibat wants to merge 2 commits into
Draft
refactor(parquet): use parquet and duckdb instead of postgresql#121bolinocroustibat wants to merge 2 commits into
bolinocroustibat wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Experimenting with a first refactor of the Tabular API data path: instead of querying PostgreSQL tables through PostgREST, resource data is now read from public Parquet files with DuckDB.
Resource metadata still comes from
tables_indexvia PostgREST, and the Metrics API is unchanged. This version has no local Parquet cache, DuckDB hits the remote (or configured) Parquet URL directly, so we can validate the approach before optimizing further.