How are tags propagated for new assets?

Tag propagation is disabled by default in Atlan. If you have enabled tag propagation, tags will be automatically propagated to a child or downstream asset created after running a workflow. This means that when a new asset is registered, tag propagation will be automatically triggered in the metastore and run as a background task.

For example, if a workflow adds an additional column to a table, a new background task for adding tags will be created in the metastore. This new task will be executed when all the previous tasks have been completed in the queue. The speed with which these tasks are completed depends on the number of pending tasks as well as the volume of tags to be added or removed. The same process also applies to tag deletion and updating tags through playbooks.

Related articles

Was this article helpful?
0 out of 0 found this helpful