DBAPI does not add tracing spans to additional page fetches #1791
Labels
api: bigquery
Issues related to the googleapis/python-bigquery API.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Environment details
Darwin M-C02D404FMD6T 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:10 PST 2023; root:xnu-10002.61.3~2/RELEASE_X86_64 x86_64
Python 3.11.3
google-cloud-bigquery
version:Version: 3.15.0
Steps to reproduce
I will try to add a self contained repro, but I'm newer to this library/python, so I will summarize in the meantime.
We have been using the opentelemetry integration along with GCP Cloud Trace to reduce latency of an application using
python-bigquery
and have noticed when there is more than one page worth of results in a DB-API cursor, we will only see trace spans for the initialbq.query
andjob.reload
calls, but not for the fetching of the additional pages, which leaves an unexplained gap in the trace timeline (see pic)To reproduce, run a DB-API query with
array_size
python-bigquery/google/cloud/bigquery/dbapi/cursor.py
Line 76 in 955a4cd
Code example
subset of flame graph from my debugging. this segment of calls appears not to generate any tracing spans (despite using bigquery_storage_client)
Thanks!
The text was updated successfully, but these errors were encountered: