-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Quickstart starts a Datahub version without matching PyPi packages for dbt #12538
Comments
Tried again this morning, and not getting the original error anymore. However, I am now getting the below error, which seems to still be about quickstart not installing the proper dependencies for dbt:
|
I have the same issue with a SAP HANA connection.
|
This is due to the fact that there is no release candidate for 1.0 of the Python package available on PyPi yet: https://pypi.org/project/acryl-datahub/#history |
I don't understand what you mean. The quickstart is using 1.0.0rc1, which is the problem. No pypi packages yet. There should be an option for quickstart to use another github tag/version. |
This was an oversight on our part - we've cut the pypi rc release now: https://pypi.org/project/acryl-datahub/1.0.0rc1/ Also note that there's a "default cli version" config that you can use to override these defaults in the future. It's configurable globally with the |
Describe the bug
When running the
datahub docker quickstart
and attempting to ingest dbt metadata objects, it cannot create a virtual env since there is no corresponding PyPi packages. Below is how this problem presents itself when trying to ingest metadata from dbt.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Ingestion in the quickstart version works. Quickstart uses a fully supported version. Alternatively update the documentation to cover this issue.
Desktop (please complete the following information):
Additional context
This seems very similar to this bug report for Postgres, which was resolved back in September 2024.
The text was updated successfully, but these errors were encountered: