yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-09-02 13:43:22 +00:00
Code Issues Packages Projects Releases Wiki Activity
OpenMetadata/openmetadata-docs/content/openmetadata/connectors/database/snowflake/index.md
Onkar Ravgan 8d56cb99b7
Optimize usage queries (#6837) 
* Snowflake usage query optimized

* Added docs for snowflake query

* Updated docs

Co-authored-by: Onkar Ravgan <onkarravgan@Onkars-MacBook-Pro.local>
2022-08-23 12:54:34 +05:30

2.2 KiB
Raw Blame History

title slug
Snowflake /openmetadata/connectors/database/snowflake

While running the usage workflow, Openmetadata fetches the query logs by querying snowflake.account_usage.query_history table.

For this the snowflake user should be granted the ACCOUNTADMIN role (or a role granted IMPORTED PRIVILEGES on the database)

Connection Options

  • Username: Specify the User to connect to Snowflake. It should have enough privileges to read all the metadata.
  • Password: Password to connect to Snowflake.
  • Account: Enter the details for the Snowflake Account.
  • Role (Optional): Enter the details of the Snowflake Account Role. This is an optional detail.
  • Warehouse: Warehouse name.
  • Database (Optional): The database of the data source is an optional parameter, if you would like to restrict the metadata reading to a single database. If left blank, OpenMetadata ingestion attempts to scan all the databases.
  • Private Key (Optional): Connection to Snowflake instance via Private Key.
  • Snowflake Passphrase Key (Optional): Snowflake Passphrase Key used with Private Key.
  • Connection Options (Optional): Enter the details for any additional connection options that can be sent to Snowflake during the connection. These details must be added as Key-Value pairs.
  • Connection Arguments (Optional): Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Snowflake during the connection. These details must be added as Key-Value pairs.
    • In case you are using Single-Sign-On (SSO) for authentication, add the authenticator details in the Connection Arguments as a Key-Value pair as follows: "authenticator" : "sso_login_url"
    • In case you authenticate with SSO using an external browser popup, then add the authenticator details in the Connection Arguments as a Key-Value pair as follows: "authenticator" : "externalbrowser"