-
Notifications
You must be signed in to change notification settings - Fork 2.1k
build: Set up ducklake catalog in dev environment #41863
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
8 files reviewed, no comments
|
Size Change: 0 B Total Size: 3.4 MB ℹ️ View Unchanged
|
| if ! python3 - <<'PY' >/dev/null 2>&1 | ||
| import duckdb # noqa: F401 | ||
| PY | ||
| then | ||
| echo "DuckLake requires the duckdb Python package." | ||
| echo "Run 'uv sync --active' (or activate Flox) before executing hogli start." | ||
| exit 1 | ||
| fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd argue we don't need to check for things that are in Python deps and installed with uv since that is pretty much a given they should be present.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On new environment this would not trigger because people would run uv sync as part of setup process. But on an existing dev environment, if I'm not mistaken, people are not expected to run uv sync --active every time, and hogli start will fail.
EDsCODE
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
works great (tested in existing environment)
2da0e52 to
54ae59c
Compare
Problem
As first step for https://docs.google.com/document/d/1bBrl2plIXPqvrdZMyqABrg2ffPxEou5INBka-DArFiI/edit?tab=t.0#heading=h.2d3rsn8s6297
This sets up duck lake catalog and storage inside existing Postgres and MinIO dev containers.
How did you test this code?
It is fully automagic for new environment setup using flox, and requires manual
uv sync --activefor existing environment.Reviewer please try hogli start to verify error message on uv sync --active, and verify everything else runs after running
uv sync --activewith "DuckLake is up!" in log messages.