Is there any way to treat a BigQuery "External Connection" like a BQ database for which views can be authorized?
I have a Cloud SQL DB that I'm accessing via an "external connection" in BigQuery. I have a BigQuery Dataset that contains a view that is essentially just select * from external_db; I'd like to keep access to that view and the external connection limited, but I'd like to make a second Dataset with a view such as select field 1, field2 from view1(or external_db); that I can give others read access to.
select field 1, field2 from external_dbin the separate Bigquery dataset, assigning appropriate access control to the users, wouldn't it be sufficient here? - Nick_Kh