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
{{ message }}
This repository has been archived by the owner. It is now read-only.
In larger deployments of Superset, it can be difficult to know which tables, datasources, and metrics are the correct ones to use. Many entities may have similar names, but no structured way exists to find the single source of truth.
Proposed Functionality
I propose the addition of a certified field on various data entities (tables and sql_metrics to start). Certification represents the review of a data entity by someone (a person, a group, a process) which adds an additional level of trust and verification to the entity.
Motivation / Problem to Solve
In larger deployments of Superset, it can be difficult to know which tables, datasources, and metrics are the correct ones to use. Many entities may have similar names, but no structured way exists to find the single source of truth.
Proposed Functionality
I propose the addition of a certified field on various data entities (tables and sql_metrics to start). Certification represents the review of a data entity by someone (a person, a group, a process) which adds an additional level of trust and verification to the entity.
See apache/superset#10591 for full details
The text was updated successfully, but these errors were encountered: