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 Apr 1, 2026. It is now read-only.
I was wondering if there were plans to expose the ability to pass bound parameters (either named or qmark style) when constructing constructing a bigframes DataFrame e.g. via Session.read_gbq_query? My understanding is they would need to be thread through to the queryParameters field on the QueryJobConfig that gets constructed.
I realize it's probably a bit of a niche use-case since this is a code-based API but for context we were looking to integrate support for bigframes in a product that allows users to build Python notebook-based interactive apps which may be used by external/untrusted users (not the ones writing the app/code) and so our SQL functionality relies on using parameterization whenever these kinds of inputs are involved.
I was wondering if there were plans to expose the ability to pass bound parameters (either named or qmark style) when constructing constructing a bigframes DataFrame e.g. via
Session.read_gbq_query? My understanding is they would need to be thread through to thequeryParametersfield on theQueryJobConfigthat gets constructed.I realize it's probably a bit of a niche use-case since this is a code-based API but for context we were looking to integrate support for bigframes in a product that allows users to build Python notebook-based interactive apps which may be used by external/untrusted users (not the ones writing the app/code) and so our SQL functionality relies on using parameterization whenever these kinds of inputs are involved.