-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changed column descriptions are not propagated #68
Comments
Valid statement. However I think overwriting descriptions should only be done explicitly. So what we really want here is a I think we can piggyback of dbt's API or use a subprocess with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I apologize in advance if my statement is not valid or if this issue has already been raised before. I wasn't able to find it myself.
I understand that column descriptions don't overwrite the descriptions that already exist downstream. This behavior is suitable for the first run and for runs involving newly created columns.
However, if a column description was previously propagated and later changed, the downstream descriptions remain unchanged.
I believe there should be an option to compare previously created artifacts and detect changes in a similar way to how DBT does it with the --defer selector. In this case, if one of the parent models has a changed description and all of its children previously had the same description as the parent, it should be safe to overwrite the children's descriptions as well.
I hope my suggestion is clear and it would be great to have this functionality implemented.
Thank you for your attention.
The text was updated successfully, but these errors were encountered: