How Kedro handles your inputs
Passing inputs into kedro is a key concept. Understanding how it accepts a
single catalog key as input is quite trivial that easily makes sense, but
passing a list or dictionary of catalog entries can be a bit confusing.
*args/**args review # [1]
Check out this post for a review of how *args **kwargs work in python.
understanding python *args and **kwargs [2]
python args and kwargs [3] article by @_waylonwalker [4]
All Kedro inputs are catalog Entries # [5]
When kedro runs your pipeline it uses the catalog to imperatively load your data, meaning that you don’t tell kedro how to load your data, you tell it where your data is and what type it is. These catalog entries are like a key-value store. You just need to give the key when setting up a node.
Single Inputs # [6]
These are fairly straightforward to understand. In the example below when kedro runs the pipeline it will load the input from the catalog, then pass that input to the func, then save the returned value to the out...