Hi Team, I am developing a kedro pipeline in whic...
# questions
a
Hi Team, I am developing a kedro pipeline in which I pass around
MemoryDataSet
from nodes. By default kedro, deep copies the memoery dataset which leads to loss of information so I created a catalog entry with
copy_mode
set to
assign
. This solves our basic problem of objects being retained as is but messes up the DAG order displayed in kedro viz. Any solutions?
n
This shouldn’t happened, how is the DAG changed in the frontend viz? Can you provide some screenshot maybe?
And also which version of kedro and kedro-viz you are using?
a
Apologies, issue got resolved 😅 🤦 Works wonders now! Thanks @Nok Lam Chan 🙂
n
That’s great! Do you know what was the issue?
Also we are working on a new feature called dataset factory, which will help a lot for reducing these boilerplate, it’s gonna make default dataset easier, stay tune!
a
Yep, the fact that I am new to kedro and forgot to click on base grouping name "icon" for MemoryDataSets rendered in kedro viz 😂 I have all my datasets named as
atw.dataset1
,
atw.dataset2
... So these got grouped together and all nodes showed up at the same level without dependancy/connections 🤦
d
can you change to a
-
instead of your
.
prefix delimiter, I think this is interfering with a diff feature in Viz ?
a
@datajoely Yep now grouping doesn't occur. Can you explain a bit more why this happens?
n
The notation of
.
has special meaning of modular pipeline in Kedro
d
@Nok Lam Chan we should build in some validation Viz side so users dont fall into this trap?
n
This would be nice, but I am unsure if it can be done easily and it may involves more than just viz. We don’t have something called a
ModularPipeline
, it’s just a pipeline afterall. Something like
my_pipeline.abc
is totally valid in
catalog.yml