This will create an Embed token and override the properties specified for specific dataset(s) serviced by the Snowflake 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 Snowflake connection are as follows
Connection ID: The ID of the Connection to be overridden. Retrieve the ID to specify as detailed here
host: The new account name of your Snowflake account to connect to
key: The username of the Snowflake user
private_key: The private key of the Snowflake user, in case key-pair auth is used (recommended!)
token: The passphrase used for the private key, in case key-pair auth is used (recommended!), or the password of the Snowflake user, in case username/password auth is used (legacy)
warehouse: The new Snowflake warehouse to use to query data
role: The new Snowflake user Role to use to query data
schema: The new database to query
table: The new snowflake table to query. The table is a concatenation of the schema and table like this <new_schema_name>.<table_name>
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: The new database to query
table: The new snowflake table to query. The table is a concatenation of the schema and table like this <new_schema_name>.<table_name>
sql: The new SQL query to run (only for SQL datasets). Alternatively, you could also use parameterized SQL Datasets .
pkg:maven/com.luzmo/sdk@1.0.0