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.

Sign up for GitHub

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

Jump to bottom

docs(bigquery): add client thread-safety documentation #132

Merged
merged 3 commits into from Jun 15, 2020
Merged

docs(bigquery): add client thread-safety documentation #132

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f9d020f
docs(bigquery): add client thread-safety documentation
HemangChothani Jun 11, 2020
b038585
docs(bigquery): nit
HemangChothani Jun 12, 2020
6354f7b
docs(bigquery): nit
HemangChothani Jun 12, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/index.rst
View file
Open in desktop
@@ -1,5 +1,14 @@
.. include:: README.rst

.. note::

Because the bigquery client uses the third-party :mod:`requests` library
plamut marked this conversation as resolved.
Show resolved Hide resolved
by default and the bigquery-storage client uses :mod:`grpcio` library,
both are safe to share instances across threads. In multiprocessing
scenarios, best practice is to create client instances *after*
plamut marked this conversation as resolved.
Show resolved Hide resolved
:class:`multiprocessing.Pool` or :class:`multiprocessing.Process` invokes
:func:`os.fork`.

More Examples
~~~~~~~~~~~~~

Expand Down