Import Tools

​

Looker

Convert a LookML repository to Honeydew semantics.

Automatic conversion steps:

1. Views are converted to Entities
2. Explores are converted to Domains
3. Relations are detected from explore join configurations
4. Measures are converted to Metrics
5. Dimensions are converted to table attributes (as part of their entity) or to Calculated Attributes - depending on their expression
6. Dimension Groups are converted to multiple attributes
7. Metadata (such as descriptions and display names) are imported as part of the conversion

Limitations:

• Liquify templates are not converted
• Looker Parameters and User attributes conversion is not automatic. They can be manually converted to Parameters
• Explores that perform conflicting joins between same tables (i.e. one explore defines the join as left while another explore defines it as inner) will convert to a single relation using one of the configurations. The additional relations can be built with Roles, and used in a domain as an active role.
• Some Looker advanced functionality is not supported as-is (such as sql_where join filters) and requires manual conversion.

​

Tableau

Convert a Tableau data source to Honeydew semantics.

Automatic conversion steps:

1. Tables are converted to Entities
2. Joins are converted to Relations
3. Table fields are converted to table attributes (as part of the entity)
4. Calculated fields with aggregations are converted to Metrics
5. Calculated dimensions are converted to Calculated Attributes
6. Level of detail (LOD) expressions are converted to Metrics with Level Of Details
7. Parameters are converted to Parameters
8. Metadata (such as descriptions, folders and display names) is imported as part of the conversion

Limitations:

• Most but not all Tableau functions are converted to Snowflake SQL; some require manual adjustment.
• Extracts with a relational schema can’t be mapped to their Snowflake source and require manual adjustment of Entity Source Tables.
• Some advanced Tableau functionality requires manual conversion.

​

Power BI

Convert a Power BI Semantic Model to Honeydew semantics.

Automatic conversion steps:

1. Tables are converted to Entities
2. Joins are converted to Relations
3. Table fields are converted to table attributes (as part of the entity)
4. Metadata (such as descriptions, folders and display names) is imported as part of the conversion

Limitations:

• Calculated DAX columns and measures are copied without conversion to SQL, and require manual conversion.
• Data source that resides in Fabric or is loaded to a Data Import, can’t be mapped to the Snowflake source automatically and requires manual adjustment of Entity Source Tables.

​

dbt

Map a dbt manifest to a Honeydew schema.

Unlike conversion from BI (Tableau, Looker or Power BI), Honeydew does not replace dbt transformations, but allows to add a semantic model on top of them.

Honeydew dbt import tool processes the compiled dbt manifest (manifest.json) to extract metadata. dbt tests are used to detect relationships and keys.

1. Chosen dbt models are mapped to Entities
2. Entity keys are detected based on unique dbt tests, if these exist
3. Relations are detected based on relationship dbt tests, if these exist
4. Metadata (such as descriptions, folders and display names) is imported as part of the conversion

​

Snowflake Schema

When mapping Snowflake tables in Honeydew UI, Honeydew automatically extracts relevant metadata if defined, such as comments, primary keys or foreign keys.