Support jobCreationMode: JOB_CREATION_OPTIONAL for BigQuery connections

What is the problem or goal the end user is trying to solve or accomplish?

The user wants to reduce latency for lightweight, repeated queries — especially those powering dashboards or data exploration — by leveraging BigQuery’s JOB_CREATION_OPTIONAL mode. This setting allows BigQuery to skip job creation when it’s not necessary, which can significantly improve performance for dashboarding workloads.

How are they solving it currently?

There is currently no workaround. Superset (and by extension, Preset) connects to BigQuery via SQLAlchemy and DB-API, which do not expose the jobCreationMode parameter used in BigQuery’s REST API. As a result, all queries go through the default job-based path, even when unnecessary.

What is the recommended solution by the Customer?

The customer is asking whether there’s a way to configure this via the "Advanced settings" in the BigQuery database connection. Ideally, there would be a way to pass job-level parameters (like jobCreationMode) via connection config or by customizing query execution in the BigQuery engine.