This will create an Embed token and override the properties specified for the BigQuery connection When doing connection overrides, it's important that the schema of the tables in the override conform to the same schema as the original datasets to avoid query failures due to schema mismatches The fields available for overriding a Bigquery connection are as follows
Connection ID: The ID of the Connection to be overridden. Retrieve the ID to specify as detailed here
key: The new IAM Service account 'client-email'
token: The new IAM Service account 'private-key'. Make sure to escape /n newline characters in the token
schema: A concatenation of a Bigquery project and dataset identifier, separated by a colon ':' (i.e. <bigquery_project_id>:<bigquery_dataset> )
table: The new Bigquery table to query. NOTE: the columns from this table need to conform to the same schema as the original dataset to avoid query failures due to schema mismatches
datasets: List of dataset-level overrides. Useful if you want to override only a single dataset in your dashboard or if you have a separate table per client. The SQL query of the dataset can also be overridden if it's a SQL dataset within Luzmo
schema: A concatenation of a Bigquery project and dataset identifier, separated by a colon ':' (i.e. <bigquery_project_id>:<bigquery_dataset> )
table: The new Bigquery table to query. NOTE: the columns from this table need to conform to the same schema as the original dataset to avoid query failures due to schema mismatches
sql: The new SQL query to run (only for SQL datasets). Alternatively, you could also use parameterized SQL Datasets .
npm install @luzmo/nodejs-sdk