Skip to content
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

Superset doesn't start when Google SDKs are installed #25548

Closed
3 tasks done
skion opened this issue Oct 6, 2023 · 0 comments · Fixed by #25550
Closed
3 tasks done

Superset doesn't start when Google SDKs are installed #25548

skion opened this issue Oct 6, 2023 · 0 comments · Fixed by #25550

Comments

@skion
Copy link
Contributor

skion commented Oct 6, 2023

A clear and concise description of what the bug is.

How to reproduce the bug

Observe that the import in bigqeuery.py results in a ModuleNotFoundError.

>>> from google.cloud import bigquery
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'google.cloud'

Install google-cloud-core, or any Google SDK which depends on it (except BigQuery):

pip install google-cloud-core

Observe that now the exception has changed to the higher-level ImportError:

>>> from google.cloud import bigquery
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'bigquery' from 'google.cloud' (unknown location)

Expected results

Missing import exception is caught and Superset loads correctly when Google SDKs have been installed but without BigQuery.

Actual results

Missing import exception is not caught, Superset doesn't load and emits the following error:

{"errors": [{"message": "cannot import name 'bigquery' from 'google.cloud' (unknown location)", "error_type": "GENERIC_BACKEND_ERROR", "level": "error", "extra": {"issue_codes": [{"code": 1011, "message": "Issue 1011 - Superset encountered an unexpected error."}]}}]}

Environment

  • superset version: Superset 0.0.0-dev, git commit ff95d0f
  • python version: Python 3.11.4
  • node.js version: v18.13.0

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant