Scott Arbeitman

➕ We have had success reimplementing the table materialisation in our project: ``` {% materialization table, adapter='presto' -%} {%- set identifier = model['alias'] -%} {%- set old_relation = adapter.get_relation(database=database, schema=schema,...

+1

We've been doing some additional thinking and investigation here, so just sharing in case it is helpful. 1. If using EMR, AWS sets the relevant Hive catalog properties as follows:...

@wrborigin Are you using EMR? We've also found (and AWS support has been able to replicate) an issue where Presto on EMR doesn't cache at all when using the Glue...

For those who might stumble upon this issue, there's a hidden property for Presto on EMR that will enable caching when using the Glue Catalog: ``` hive.metastore.glue.shared-metastore-cache-enabled=true ``` This is...

I looked into this a bit more closely. [`add_query`](https://github.com/dbt-labs/dbt-presto/blob/cc834028f8120784829cc66733007dbabcec1a30/dbt/adapters/presto/connections.py#L189) splits the SQL it receives by `;`, then sends each one to be executed. However, with `prestodb` library, the only way...

I have the same issue. Did you ever figure out a fix?

The would work but would emit the password in the logs. It's a little more secure and only slightly more verbose using `_env` in each task. You can also use...

I think the more generic pattern would be joining the results of multiple questions. Even in a single data warehouse where you have multiple fact tables with different dimensions, being...

Best I can tell, this is a timeout on an API call, and Spectacles just returns a very generic message. We are currently hitting the same problem. Are you using...