Skip to content

Tag Removal Behavior

When a tag is removed in Collibra, the connector reflects the change in Ranger on the next successful sync. The resource-mapping removals below happen automatically and are not configurable; whether an orphaned tag definition is also deleted is controlled by Tag Definition Deletion. All removals are subject to the Scan-Failure Safeguards — an incomplete or suspicious scan never triggers deletes.

How removals are applied

Scenario What the connector does in Ranger
A tag is removed from an asset that still has other tags The resource mapping for that asset is re-pushed with the remaining tags.
A tag's last mapping on an asset is removed The resource mapping is deleted from Ranger using importservicetags with op=delete.
A tag is no longer used by any synced asset After its mappings are cleared, the tag definition is deleted from Ranger (DELETE /service/tags/tagdef/{id}) only when tag-definition deletion is enabled (tag.sync.skip.delete.tagdefs=false, the default for Collibra). When it is true, the mappings are still removed but the tag definition is kept. See Tag Definition Deletion.

Safety guarantee

When tag-definition deletion is enabled, Ranger still refuses to delete a tag definition that is mapped to a resource — including resources owned by another service or connector on the same Ranger. Because of this, a tag that is still in use elsewhere is left intact even if this connector no longer uses it. Such a rejection is logged and skipped; it does not fail the sync.

This means tag-definition cleanup is safe by design: only tags that are genuinely unmapped everywhere are removed.