Add support render for versioned dbt models.

[binhnq94]

Description

Model version is supported by dbt-core >= 1.5.
As cosmos v1.1.0a1, it not support to render task for model have versions.

In this PR I propose to use node_dict["alias"] as DbtNode.name instead of node_dict["name"] if node_dict["resource_type"] == model.

This PR also help cosmos render the names of nodes to be correctly the same as identifier if users config alias or custom the generate_alias_name macro. Refer: alias document and the generate_alias_name implementation.

Related Issue(s)

#260

Breaking Change?

When model have version config, each model version will create a database relation with alias <model_name>_v<v>, for examples: dim_customers_v1, dim_customers_v2...

So I expected that cosmos will created run/test tasks for each versions, for example: dim_customers_v1_run, dim_customers_v2_run, dim_customers_v1_test, dim_customers_v2_test...

The second expectation is the dag will render right depedences, for example: stg_customers_v1 >> customers_v1, stg_customers_v2 >> customer_v2...

Checklist

• I have made corresponding changes to the documentation (if required)
• I have added tests that prove my fix is effective or that my feature works

[netlify]

👷 Deploy Preview for amazing-pothos-a3bca0 processing.

Name	Link
🔨 Latest commit	898569e
🔍 Latest deploy log	https://app.netlify.com/sites/amazing-pothos-a3bca0/deploys/6516fb7836da88000811009d

[tatiana]

@binhnq94, thanks a lot for your contribution!

I will still read the docs to understand more about aliases and versions, but I have two initial questions:

1. Would there be any benefit in introducing a new attribute to DbtNode called alias instead of overloading the property name with two possible sources? We could also introduce an identifier if it helped. What are the pros and cons of overriding name?
2. When we render dbt nodes as Airflow nodes, what would be the benefit of rendering models using aliases instead of their names?

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (fabedd8) 92.83% compared to head (898569e) 92.83%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #516   +/-   ##
=======================================
  Coverage   92.83%   92.83%           
=======================================
  Files          49       49           
  Lines        1983     1983           
=======================================
  Hits         1841     1841           
  Misses        142      142           

Files	Coverage Δ
cosmos/dbt/graph.py	98.78% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[binhnq94]

@binhnq94, thanks a lot for your contribution!

I will still read the docs to understand more about aliases and versions, but I have two initial questions:

1. Would there be any benefit in introducing a new attribute to DbtNode called alias instead of overloading the property name with two possible sources? We could also introduce an identifier if it helped. What are the pros and cons of overriding name?
2. When we render dbt nodes as Airflow nodes, what would be the benefit of rendering models using aliases instead of their names?

1. No, because if you use model versions in dbt project, name is not unique any more. dbt run with --models <name> will build all model versions leading to select not work as expected.
2. Use alias, cosmos will render the DAG that have the same lineage as in the docs created by dbt docs generate cli. . It help users to double check easier and it support model versions.

[tatiana]

@binhnq94 let's aim to have this change released as part of 1.2. Please, let me know if you'd like any further support on anything - I'm looking forward to merging this change.

[binhnq94]

@tatiana I fixed the error: improper relation name (too many dotted names) in commit
by deleting the macro file drop_table.sql.

[binhnq94]

@tatiana I have already fixed the fail in integrate tests (sorry, last time I only run model_version dag only.)

Let trigger integration tests :'(

[tatiana]

This was released as part of 1.2:

• https://pypi.org/project/astronomer-cosmos/1.2.0/
• https://github.com/astronomer/astronomer-cosmos/releases/tag/astronomer-cosmos-v1.2.0
  cc @binhnq94