Cross-entity depedencies in Falcon are important because a dependency cannot be removed until all the dependents are first removed. For example, if Falcon manages two clusters, one in Oregon and one in Virginia, and the Oregon cluster is going to be taken down, you must first resolve the Virginia cluster dependencies as one Dataset (Dataset 3) has a cross-entity dependency and depends on Email Ingest (Process 1).
To remove the Oregon cluster, you must resolve this dependency. Before you can remove the Oregon Hadoop cluster, you must remove not only Process 1, Datasets 1 and 2 but also modify the Dataset 3 entity to remove its dependence on Process 1.
As Falcon manages more clusters, viewing these dependenices becomes more crucial. For information on viewing dependencies in Falcon, see Viewing Dependencies. For more information on Cross-Enity validations, see Falcon Community Documentation on Cross-Entity Validations.
