datalake

Syntax for changing Iceberg table properties

ALTER TABLE an-iceberg-table SET PROPERTIES a-property-name = 'a-value'

Implementation tips

Implement the method io.trino.spi.connector.ConnectorMetadata#setTableProperties in io.trino.plugin.iceberg.IcebergMetadata.

Use org.apache.iceberg.BaseTable#updateProperties for updating table properties.

Test tips

Add

As seen above, there is a lot of extra space around some screenshots in the docs.

We can still use the cool tool that adds the window-style border and controls (although you can also choose to remove it), but the extra space is hard on the eyes and makes the page read less fluently.

Which just invokes the blockingTree for each record.

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

Describe the bug

A standard item in HDFS browser has three things. (Un)fold, name, select. The name part is clickable, and even flashes on click, but doesn't do anything.

Expected behaviour

Either make it select the item, (un)fold it or don't make it clickable.

Screenshots

![May-16-2019 15-37-23](https://user-images.githubusercontent.com/17467768/57858189-e2a79280-77f0-11e9-921f-

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