Closed octiva closed 2 weeks ago
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.
Describe the feature
A clear and concise description of what you want to happen.
add a
include_tests
function that checks if each column passes thenot_null
orunique
tests, and adds them if they do. We can look to extend torelationships
&accepted_values
in the future.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
We could do this outside of the codegen, eg. Do as suggested by just doing bad things to the yaml and running tests on columns.
Additional context
Is this feature database-specific? Which database(s) is/are relevant? Please include any other relevant context here.
Who will this benefit?
What kind of use case will this feature be useful for? Please be specific and provide examples, this will help us prioritize properly.
Are you interested in contributing this feature?
Yeah I would be interested. I have recently contributed to
astronomer-cosmos
&dbt-athena
.If any main contributors want to suggest implementation details I would be keen. My TLDR thought is: run test for each test type (so we can extend if we want), if test passes, include it, if not, dont.