You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DP2: which depends on the output port of DP1. This dependency is explicitly declared using the "x-dependsOn" or "dependsOn" field on DP2's input port. Using Blindata's Observer, this dependency is clearly visible in the lineage of the two DPs.
When DP1 changes the FQN of its output port on which DP2 depends (e.g., due to a version update), the dependency is lost. Consequently, the lineage in Blindata is also lost.
It would be useful to implement a notification mechanism to inform the owner of DP2 that the dependency has been lost. One idea could be to leverage Blindata's notification system to ensure all involved parties are notified.
The text was updated successfully, but these errors were encountered:
Considering the situation where two DPs exist:
DP1
: which has an output portDP2
: which depends on the output port of DP1. This dependency is explicitly declared using the "x-dependsOn" or "dependsOn" field onDP2
's input port. Using Blindata's Observer, this dependency is clearly visible in the lineage of the two DPs.When
DP1
changes the FQN of its output port on whichDP2
depends (e.g., due to a version update), the dependency is lost. Consequently, the lineage in Blindata is also lost.It would be useful to implement a notification mechanism to inform the owner of
DP2
that the dependency has been lost. One idea could be to leverage Blindata's notification system to ensure all involved parties are notified.The text was updated successfully, but these errors were encountered: