Governance
Governance in Gravitino is three things attached to metadata: tags that classify it, policies that state rules about it, and owners who are accountable for it. The UI summarizes how much of a metalake carries each, so gaps show up as numbers rather than as surprises in an audit.
Quick Start
1. Tag what needs classifying. Tags attached to a catalog or schema reach everything beneath it. See Tags.
2. Attach policies. See Policies.
3. Give every asset an owner. Owners are set on the object, or inherited by creation. See Access Control.
4. Read the coverage. The overview shows how many assets are tagged, owned, and covered by a policy, overall, per catalog, and per asset type.
What the Overview Shows
| Figure | What It Counts |
|---|---|
| Assets | Tables, views, functions, filesets, topics, and models in the metalake |
| Unowned assets | Assets with no owner |
| Policies | Policies defined in the metalake |
| Assets without a policy | Assets that no policy reaches, directly or through an ancestor |
Coverage is broken down two ways. By catalog, the catalogs with the lowest coverage come first, since those are where the gaps are. By type, the same measures are split across tables, views, functions, filesets, topics, and models.
An asset counts as tagged or covered by a policy when it carries one directly or inherits one from its schema or catalog, the same way the object itself resolves them.
When the Figures Update
The figures come from a collection that runs when the server starts and then once a day at midnight server time. They are not recalculated when a tag, policy, or owner changes, so a change appears on the overview after the next collection. A server that has just started shows that no metrics have been collected until the first collection finishes.
A restart also runs a collection. The objects themselves always reflect a change immediately; only the summary lags.