Skip to content
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

[FEATURE] Exposures.yml to Lineage #393

Open
smithbc25 opened this issue Mar 22, 2023 · 0 comments
Open

[FEATURE] Exposures.yml to Lineage #393

smithbc25 opened this issue Mar 22, 2023 · 0 comments

Comments

@smithbc25
Copy link

What are you trying to do?
I'd love to see exposures defined in the exposures.yml added to lineages. This would be a huge win because it allows for prioritizing triaging test failures by looking at the most mature exposures first. For example, if there is a test error on a model that is feeding our external facing product, that is a 'drop everything' response. However, if the model is only being used for internal reporting, it may have a end of day or end of week prioritization. Having this available in re_data instead of trekking back to docs to understand impacts of test failures would be a big win.

Describe the solution you’d like
When looking at the lineages tab and table lineage, have exposures be included.

Describe the alternative you’ve considered or used
No alternative.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant