You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 6, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 6, 2026. It is now read-only.
Is your feature request related to a problem? Please describe.
When running the %%bigquery magics, there is no indication of progress.
Describe the solution you'd like
Show a progress bar using tqdm or tqdm_notebook.
Describe alternatives you've considered
N/A
Additional context
tqdm_notebook is ideal, as it uses the ability to embed HTML for a nicer-looking progress bar, but this is not always available. tqdm should be the default, but perhaps overridable via the google.cloud.bigquery.magics.context settings.
but ideally we would want the ability to change to tqdm_notebook when explicitly requested or maybe even if we can detect that we are in a supported environment
Activity
tswast commentedon Nov 16, 2020
This may be as simple as setting
progress_bar_type="tqdm"here:python-bigquery/google/cloud/bigquery/magics/magics.py
Line 692 in dc78edd
python-bigquery/google/cloud/bigquery/magics/magics.py
Line 695 in dc78edd
but ideally we would want the ability to change to
tqdm_notebookwhen explicitly requested or maybe even if we can detect that we are in a supported environmenttswast commentedon Nov 16, 2020
Follow-up to #343 which added the progress bar for waiting for the query to finish.
HemangChothani commentedon Nov 19, 2020
Can we use
get_ipython().__class__to detect terminal or any other notebooks and set the progress_bar_type accordingly?Can we include
progress_bar_typeparameter in to the magic_arguments and set default to 'tqdm'?tswast commentedon Nov 19, 2020
Let's start with this. Plus, let's add
progress_bar_typeto the global context object so that the default can be changed by the user.Let's file a separate issue for that. I don't want to get too magic in our magics. :-)