Administrators can define lineage relations manually, without platform ingestion, a development framework, or script parsing. Navigate to Settings > Lineage > Configuration to configure: spaces and applications mappings, asset mappings, and the pool of available assets.
For the other lineage methods and when to use each, see Sources of data lineage.
Only admin users can configure lineages.
Mapping spaces and applications
The Spaces & applications panel maps a source space and application to a target space and application under a chosen lineage method. The method determines which lineage relations the mapping applies to.
The table lists every existing mapping:
| Column | Contains |
|---|---|
| From space | The source space of the mapping. |
| From application | The source application within the source space. |
| Method | The lineage method the mapping applies to. |
| To space | The target space of the mapping. |
| To application | The target application within the target space. |
To create a mapping, click Add mapping, then select the source space and application, the lineage method, and the target space and application. To remove a mapping, use the delete action in its row.
Uniqueness rules for space and application mappings
A mapping is unique on the combination of source space, source application, lineage method, target space, and target application.
| Situation | Result |
|---|---|
| The same source and target space and application pair, mapped again under a different method. | Allowed. |
| The same source and target space and application pair, mapped again under the same method. | Rejected — the mapping already exists. |
| The same space and the same application on both sides of the mapping. | Rejected — a pair cannot be mapped to itself. |
A space and application pair can therefore take part in several mappings, as long as each mapping uses a different lineage method.
Mapping lineage assets
The Assets mapping panel maps one lineage asset to another. Each row shows the source asset and the target asset, together with the asset type of each side.
Use the panel to add a new asset mapping, edit an existing one, or delete it.
An asset mapping is unique on the combination of source asset and target asset. An asset cannot be mapped to itself.
Managing available assets
The Available assets panel holds the pool of lineage assets that asset mappings draw from. An asset must exist in this panel before it can be used in a mapping.
The table describes each asset:
| Column | Contains |
|---|---|
| Name | The name of the lineage asset. |
| Type | The lineage asset type. |
| Source | The origin of the asset. |
| Space | The space the asset belongs to. |
| Application | The application the asset belongs to. |
The Type and Source columns cannot be filtered.
Adding assets to the pool
Two actions add assets to the pool:
- Add tag creates a free-text tag asset. The name is required, is trimmed of surrounding whitespace, and can be up to 200 characters long.
- Add object promotes existing catalog objects into lineage assets. Only object types that have a matching lineage asset type can be added. When no object type matches, the dialog states that no objects are available.
Editing, mapping, and deleting assets
Each row in the pool offers three further actions:
- Edit tag renames a tag. The action is available on tag-type assets only.
- Quick map maps the asset in the row to another asset, without opening the Assets mapping panel.
- The delete action removes the asset from the pool.
Deleting an asset also removes every asset mapping that uses it.