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
I have searched the existing issues, and I could not find an existing issue for this feature
I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion
Describe the feature
Filing this on behalf of a customer - they would like the native dbt-core persist_docs functionality to be able to propagate upstream column descriptions to downstream ones as well without having to copy the descriptions multiple times. For example:
-- models/foo.sqlselect1 id
-- models/bar.sqlselect*from {{ ref('foo') }}
^ Right now, this means that only foo.id will have a description be applied to it - but it would be useful if dbt also automatically added col descriptions for bar.id as well.
dbt Cloud Explorer currently is able to propagate column descriptions with it's CLL.
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is this your first time submitting a feature request?
Describe the feature
Filing this on behalf of a customer - they would like the native dbt-core persist_docs functionality to be able to propagate upstream column descriptions to downstream ones as well without having to copy the descriptions multiple times. For example:
^ Right now, this means that only
foo.id
will have a description be applied to it - but it would be useful if dbt also automatically added col descriptions forbar.id
as well.dbt Cloud Explorer currently is able to propagate column descriptions with it's CLL.
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: