datalake

With Hive connector

trino:default> CREATE TABLE one (a varchar);
            -> CREATE VIEW two AS SELECT * FROM one;
CREATE TABLE
CREATE VIEW

DROP TABLE is rejected on a view:

trino:default> DROP TABLE two;
Query 20210906_150832_00015_id3y3 failed: line 1:1: Table 'hive.default.two' does not exist, but a view with that name exists. Did you mean DROP VIEW hive.default.t

The command to create a new repository from lakectl is:
lakectl repo create <repository uri> <storage namespace>

However, it is not fully clear what is the repository uri, and the help flag doesn't explain it.

If a user tries to create a repository and specifies only the name

I'm new to the idea of Data Vault 2.0 and I'm reading the Dan Linstedt book to understand it better.

To help me get a better perspective of how dbtvault works I would like to know how difficult do you think it would be to add support for BigQuery?

Are there specific features of Snowflake which makes it better for running dbt/dbtvault ?

Thanks,
Jacob

Background

We added additionalColumns to MappingConformanceRule but did not add validation of these fields on import

Feature

On Import Dataset validate extra output columns of MappingTableConformanceRule

Describe the bug
Behavior of var.enable_gluesync is broken.

• In ECS, setting enable_gluesync to false will still trigger HMS docker image to use glue sync, but the IAM policy is not created, so it fails.
• In K8S, the env var ENABLE_GLUESYNC is never passed to the HMS docker image, so enabling glue sync doesn't work.

Additional context

• The ECS issue is because when TF var