New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
live-tests: add duckdb backend #35923
live-tests: add duckdb backend #35923
Conversation
The latest updates on your projects. Learn more about Vercel for Git 鈫楋笌 1 Ignored Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @alafanechere and the rest of your teammates on Graphite |
e1cb546
to
470af72
Compare
9630662
to
644e3ea
Compare
470af72
to
f3f8112
Compare
644e3ea
to
fed1b63
Compare
It's not a present for me. This will help run comparisons at scale! |
airbyte-ci/connectors/live-tests/src/live_tests/commons/backends/duckdb_backend.py
Outdated
Show resolved
Hide resolved
I bet @aaronsteers knows a way to load into duck directly from the jsonl files |
Indeed! There's a function called read_json_auto(), which we're using in PyAirbyte. https://duckdb.org/docs/data/json/overview.html#read_json_auto-function |
84304b1
to
ee897ca
Compare
fed1b63
to
41c5bc7
Compare
41c5bc7
to
715e72e
Compare
@bleonard @aaronsteers @erohmensing thanks for your suggestion |
Small 馃巵 for @bleonard : the live testing tool persists airbyte messages to a DuckDb file.