Support additional metadata via Client_Info with BigQuery Storage Read & Write (gRPC) APIs #2296
Open
1 task done
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Determine this is the right repository
Summary of the feature request
I would like to be able to provide a
user_agent
(or alternatively "request_reason" ) metadata string to BigQuery REST APIs as well as BigQuery gRPC APIs, and have them propagated to Cloud Logging.Ideally, the metadata specification should be identical across the API surfaces and clients.
Desired code experience
An example of how this is done in BigQuery client is available here:
file: bigquery_rest.py
However, this does not work with BigQuery Storage Read / Write APIs in the same way.
Expected results
protoPayload.requestMetadata.callerSuppliedUserAgent = test_A/1.0 (lineage_id:baz;user_id:lem) ...
API client name and version
google-cloud-bigquery_storage_v1
Use case
I want to specify additional metadata that represents the workload behind my BigQuery API calls.
Additional context
The following workaround exists for using the bigquery_storage_v1 grpc api, but it is less intuitive than the Client_Info method above.
The text was updated successfully, but these errors were encountered: