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
session.run() currently returns "free outputs". What free_output means in the code is just "output that's not defined in the catalog", which is a subset of "output that's not a MemoryDataSet".
There was agreement that the "free outputs" output from session isn't very clear. It was suggested to simply return all output from nodes that is not consumed, even if it's defined in the catalog. However, this could lead to very large amounts of data being returned. Instead we'll change it to return all free outputs and additionally any MemoryDataSets that are defined in the catalog.
I think this is a bug fix, rather than any behavioral changes. This happens if someone put MemoryDataSet in the catalog and session.run removes it from the output
free_outputs=pipeline.outputs() -set(catalog.list())
# This will be changed tofree_outputs=pipelines.outputs() -set(catalog_excluding_memory_dataset.list())
Description
session.run()
currently returns "free outputs". Whatfree_output
means in the code is just "output that's not defined in the catalog", which is a subset of "output that's not a MemoryDataSet".kedro/kedro/runner/runner.py
Lines 78 to 91 in f491420
There was agreement that the "free outputs" output from session isn't very clear. It was suggested to simply return all output from nodes that is not consumed, even if it's defined in the catalog. However, this could lead to very large amounts of data being returned. Instead we'll change it to return all free outputs and additionally any MemoryDataSets that are defined in the catalog.
Context
#1802
The text was updated successfully, but these errors were encountered: