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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: