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
When querying BigQuery via Redash, the audit log on BigQuery appears to be executed by the GCP Service Account configured as the data source.
However, the actual executor is someone using that data source, and since Redash does not have the BigQuery Job ID in the query result, the history of query execution is not linked between Redash and BigQuery.
This makes it difficult to check execution results on Redash with GCP.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When querying BigQuery via Redash, the audit log on BigQuery appears to be executed by the GCP Service Account configured as the data source.
However, the actual executor is someone using that data source, and since Redash does not have the BigQuery Job ID in the query result, the history of query execution is not linked between Redash and BigQuery.
This makes it difficult to check execution results on Redash with GCP.
Beta Was this translation helpful? Give feedback.
All reactions