You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is not too much hair on it, I might try to help with the effort and send a pull request but I wanted to make sure I understood how the SQL Mesh project operates.
Warm regards,
Brandon
The text was updated successfully, but these errors were encountered:
I have not used Dremio myself but my high level understanding is that it is similar to Trino and users would likely be storing data in Iceberg. It can be run locally in a docker container and then also use the cloud offering. I will be making that assumption for the remained of my advice.
Here is a more recent-ish PR that shows the high level work involved in adding an engine: #1579
I would focus on adding for Dremio open source first since that is easier than adding a remote cloud connection:
Add a new connection config for Dremio open source
Add a new class for your connector that implemented the base engine adapter class
Once this is done then I would repeat but for Demio Cloud. Adding the cloud would likely easy since you have added the foundational support for Dremio.
It is not a trivial amount of work. If you did add the cloud support then we would also ask you about how to setup an account with that cloud so we could run our tests against it to make sure we don't break anything.
izeigerman
changed the title
What would it take to port the dbt-dremio connector over to SQL Mesh?
What would it take to port the dbt-dremio connector over to SQLMesh?
Apr 16, 2024
Hi there.
I have been using the DBT connector for Dremio Cloud over here https://github.com/dremio/dbt-dremio
What would it take to port it to SQL Mesh?
If there is not too much hair on it, I might try to help with the effort and send a pull request but I wanted to make sure I understood how the SQL Mesh project operates.
Warm regards,
Brandon
The text was updated successfully, but these errors were encountered: