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
I've always felt like Kedro misses the ability to specify additional dependencies among nodes, which are not dataset related.
Context
For instance, consider the problem of filling a knowledge graph though Kedro. Obviously, there's two main nodes:
Write nodes
Write edges
However, the edges cannot be written before the nodes were pushed. There is hence no "dataset" dependency between the nodes, but rather an execution dependency.
Possible Implementation
Adding this to Kedro would involve 1) addition to the node system and 2) and update to the topological execution mechanism. With respect to the nodes, dependencies could be specified as follows:
The current work-around is to add "artificial" dataset dependencies among the nodes. This has the drawback that the function signatures of those nodes are polluted.
The text was updated successfully, but these errors were encountered:
Hey @lvijnck good to see you pop up here 👀 congrats on the new role!
The current way to do this is to pass a dummy dataset between the nodes to coerce the DAG into the right shape.
There are some open proposals on a more explicit mechanism of defining the DAG order. #1156 , I'm 99% @noklam has a concrete design somewhere, but I can't find it
This was the issue (now discussion) I was looking for, @lvijnck if you have any further thoughts please add them there as it really helps prioritise things
Description
I've always felt like Kedro misses the ability to specify additional dependencies among nodes, which are not dataset related.
Context
For instance, consider the problem of filling a knowledge graph though Kedro. Obviously, there's two main nodes:
However, the edges cannot be written before the nodes were pushed. There is hence no "dataset" dependency between the nodes, but rather an execution dependency.
Possible Implementation
Adding this to Kedro would involve 1) addition to the node system and 2) and update to the topological execution mechanism. With respect to the nodes, dependencies could be specified as follows:
Possible Alternatives
The current work-around is to add "artificial" dataset dependencies among the nodes. This has the drawback that the function signatures of those nodes are polluted.
The text was updated successfully, but these errors were encountered: