datalake

When you change a query state filter e.g. showing 'Finished' queries or 'User Error' queries, the Show Limit is not respected immediately resulting in all queries being rendered. If a re-order interval is set then Show Limit is applied on the next query refresh. If there are a large number of queries in the history this can result in the browser crashing on the first render.

The following two c

Currently lakeFS register openapi handlers and handle all specific routes.
In case of a call to /api/v1/test, the unknown path under the API prefix, the mux will serve the request by the UI handler and return a valid HTML (UI) page.

The expected behaviour is to return a non-2xx status code with JSON error - prefered the internal error format, so the developer will handle an error and not fai

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