Preset Feature Feedback
What is the problem or goal the end user is trying to solve or accomplish?
With the implementation of catalogs support, it will be possible to use a single BQ connection to query and create physical datasets from multiple projects. However, the query is always executed in the target project (rather than being executed in a default project and using a cross-project join). This requires granting the Service Account access to run jobs in all projects, which results in having the query execution cost in these projects.
Users would like to be able to specify the project that the query should be executed against, to centralize cost.
How are they solving it currently?
They need to create virtual datasets in the SQL Lab.
What is the recommended solution by the Customer?
Provide the ability to specify in the BQ connection if a specific project should be used for billing purposes.
