-
Notifications
You must be signed in to change notification settings - Fork 30
Support for incremental models #5
Comments
Thanks @buremba! How are you thinking about implementing incremental models? We like to use the I think the |
@drewbanin The only way to make it work in Presto is The problem is that Presto is actually just a distributed query executor and under the hood, it has a concept of connectors which might be an RDBMS, S3, Hadoop, Elasticsearch, etc. AFAIK, only a few connectors support transactions so this feature won't be available in most of the connectors. I will look into the connectors and see which ones support transactions and will let you know. |
Are there any updates on this? |
Can we use Alter Table with a new location to simulate this? I believe the alter table statement is atomic. We will have to merge existing data with the incoming data and save it to a new location first, and use an alter table to point the original table to the new location. It has the drawback of not being space efficient(maybe a vacuum step) and only suited for infrequent batch uses |
They are working on merge into for hive: trinodb/trino#7708 |
@mdesmet I've opened an issue on the dbt-trino adapter and I'll try to have a proof-of-concept |
This is one of the killer DBT features and I think that it should be available in Presto as well. I will try to create a PR for this one but it might take a few weeks.
If there's anyone who is willing to implement this feature in less than 2 weeks, feel free to comment.
The text was updated successfully, but these errors were encountered: