Universal Resource Identifier (URI)

The Universal Resource Identifier (URI) is the unique identifier for every resource within the mapped data model. The URI is used to map the location of resources within the data model, and their connections.

The main role of the URI is to establish relationships between two resources. To illustrate with an example:

Suppose the data model has a database table with URI snowflake.us_west_2.abcd1234.my_database.my_schema.my_table . On the next run of the snowflake integration, a new view is observed at snowflake.us_west_2.abcd1234.my_database.my_schema.my_view, and that view depends on snowflake.us_west_2.abcd1234.my_database.my_schema.my_table, in this case, a relationship of type "depends" will be established between the view and the table.

URIs are always lowercase.

The following describes the structure of the URI for each resource type

URI formats by type

platform

URI structure: platform.<PLATFORM TYPE>.<PLATFORM IDENTIFIER>

Examples: platform.snowflake.abcd1234

table

URI structure:

Depending on the database technology, the URI takes one of two forms:

• <TECHNOLOGY>.<PLATFORM IDENTIFIER>.<DATABASE>.<SCHEMA>.<TABLE NAME>

• <TECHNOLOGY>.<PLATFORM IDENTIFIER>.<SCHEMA>.<TABLE NAME>

Examples:

• bigquery.my_project.my_dataset.my_table

• mysql.mysql_domain.com.my_schema.my_table

• aws_glue.aws_account_identifier.aws_region.my_glue_catalog_identifier.my_schema.my_table

looker folder

URI structure: looker.<LOOKER HOST>.folder.<LOOKER ID>

Examples: looker.my_looker_domain.folder.1001

Terms:

• TECHNOLOGY: the technology of the platform. i.e. 'snowflake', 'bigquery', 'mysql', etc.

• PLATFORM IDENTIFIER: a platform-type-specific identifier that uniquely identifies the platform. For example, for Snowflake, this would be the snowflake account id.

• DATABASE: the name of the database the table is in. In some databases, this level of the hierarchy is called "catalog".

• SCHEMA: the name of the schema the table is in. In some databases, this level of the hierarchy is called "database".

• TABLE NAME: the table's name.

• LOOKER ID: each resource in Looker has a unique id.

• PLATFORM TYPE: the type of the platform. i.e. 'snowflake', 'tableau_site', 'mysql', etc.