[Feature] dbt source rendering: Use .
instead of _
between schema & table
#1308
Labels
area:rendering
Related to rendering, like Jinja, Airflow tasks, etc
dbt:source
Primarily related to dbt source command or functionality
enhancement
New feature or request
triage-needed
Items need to be reviewed / assigned to milestone
Milestone
Description
Currently in cosmos, sources are rendered as emptyOperators with a task_id of
{schema}_{table}_source
The main issue with this naming convention is that the usual convention of naming tables with the schema uses dot (.) instead of underscore (_), and by using underscore in the naming of our tasks, it is not possible to properly identify where the schema name ends and where the table name begins.
Use case/motivation
By having a logical separation of the schema and the table, it is easy to extend cosmos and add extra features to the sources. At my company we are adding sensors before the sources, but the process becomes way harder because of something as simple as using the
_
instead of.
in the name of the task.Related issues
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: