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
Although SQLMesh provides an alternative to dbt with notable enhancements, it presently lacks a crucial functionality found in dbt: the capability to define model locations. To bridge this gap and offer users enhanced control over their data modeling workflows, I suggest integrating a feature similar to dbt's model location configuration. This improvement would empower users to precisely specify the locations of their models within Databricks, aligning with the streamlined approach established by dbt.
Benefits:
Enhanced flexibility: Users can define model locations according to their specific requirements.
Consistency with dbt: Aligning with dbt's configuration model allows for easier adoption by users familiar with dbt's practices.
DBT models location setup example (dbt_project.yml)
Description:
Although SQLMesh provides an alternative to dbt with notable enhancements, it presently lacks a crucial functionality found in dbt: the capability to define model locations. To bridge this gap and offer users enhanced control over their data modeling workflows, I suggest integrating a feature similar to dbt's model location configuration. This improvement would empower users to precisely specify the locations of their models within Databricks, aligning with the streamlined approach established by dbt.
Benefits:
Enhanced flexibility: Users can define model locations according to their specific requirements.
Consistency with dbt: Aligning with dbt's configuration model allows for easier adoption by users familiar with dbt's practices.
DBT models location setup example (dbt_project.yml)
Context: https://tobiko-data.slack.com/archives/C044BRE5W4S/p1712257465726229
The text was updated successfully, but these errors were encountered: