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
MemoryDatasets are non-persistent datasets, that are not saved after a run. Some users have flowcharts containing numerous MemoryDatasets, and Kedro-Viz currently lacks a way to show and differentiate them from persistent datasets.
This was suggested for quick experimentation by @datajoely, but related questions have been asked by slack users:
"Does anyone know how layers are inferred for datasets which are not tagged in the catalog and just exist as memory datasets.
For example: If you have a pipeline where the only elements you persist are lets say till primary layer, and then you jump to model output in the end. How will the layers be inferred in that case ?"
Context
This is particularly useful for larger and more complex pipelines, where there is a greater need to track datasets. Another benefit is that it supports the debugging of the pipeline.
Possible Implementation
The first step would be to show MemoryDatasets on the Kedro-Viz flowchart, and then the ability to filter them out of the view as required. Implementation would require:
Distinctive MemoryDataset view on flowchart [Experiment] Distinctive MemoryDataset view on flowchart #1706 - This PR introduces opacity to MemoryDatasets, making them easily distinguishable on the flowchart. The transparency also signifies their non-persistent nature.
Yes, we have prioritised for this ticket - #1148.We will explore the concept of allowing users to customise (icons/color) their dataset through the catalog.
Description
MemoryDatasets are non-persistent datasets, that are not saved after a run. Some users have flowcharts containing numerous MemoryDatasets, and Kedro-Viz currently lacks a way to show and differentiate them from persistent datasets.
This was suggested for quick experimentation by @datajoely, but related questions have been asked by slack users:
"Does anyone know how layers are inferred for datasets which are not tagged in the catalog and just exist as memory datasets.
For example: If you have a pipeline where the only elements you persist are lets say till primary layer, and then you jump to model output in the end. How will the layers be inferred in that case ?"
Context
This is particularly useful for larger and more complex pipelines, where there is a greater need to track datasets. Another benefit is that it supports the debugging of the pipeline.
Possible Implementation
The first step would be to show MemoryDatasets on the Kedro-Viz flowchart, and then the ability to filter them out of the view as required. Implementation would require:
@rashidakanchwala has created two experimental PRs to address this:
Acceptance Criteria
The text was updated successfully, but these errors were encountered: