Repository navigation
Add the QuestDB Parquet three readers example - #7
Merged
Merged
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
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.
Companion example for the blog post "One table, three readers: QuestDB, Polars and DuckDB on the same Parquet" (questdb/questdb.io#3049).
./qdb_rootso the Parquet partition files can be read from the hostwalkthrough.pyloads 1.5M synthetic FX trades from a Polars DataFrame, builds a one-minute materialized view, converts three days to Parquet, and checks QuestDB SQL, Polars and DuckDB against the DataFrame that was sentCOPY ... WITH FORMAT PARQUETexportrequirements.txtNot to be merged until the post is ready to publish.