-
Notifications
You must be signed in to change notification settings - Fork 915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data versioning YAML API via catalog.yml #2662
Comments
Hello @Christophe-pere , sorry for the delay! Could you please raise this issue over https://github.com/Galileo-Galilei/kedro-mlflow? cc @Galileo-Galilei |
Hi, In fact, I just fixed this issue. To be able to version a dataset, it requires a Based on the blog https://waylonwalker.com/kedro-incremental-versioned-datasets/
This generates a new folder with a new yaml file
And now, the preprocessed data will be versioned. I haven't found this command in the documentation or it was unclear to me. But now, it's working. |
xref #2604 |
Regarding
It likely either store the data but not where you want (and certainly not the |
Description
Hi,
I tried creating versions for the dataset I used in an ML experiment, but I got an error following the tutorial documentation.
Context
I created a pipeline to benchmark different models in the same flow structure. Everything work and I can track the metrics in the
kedro-viz
environment. When I tried to version the dataset as mentioned in the documentation:https://kedro-mlflow.readthedocs.io/en/stable/source/07_python_objects/01_DataSets.html
I got a
VersionNotFoundError,
which stopped the pipeline.I also tried via
kedro-mlflow
via the YAML API, the pipeline runs, but nothing is stored or versioned.Steps to Reproduce
Lines in the YAML
catalog.yml
file.I then ran the pipeline with the command:
I also tried with
kedro-mlflow
plugin and wrote:And ran the same command line. The pipeline runs, but nothing is stored.
Expected Result
Dataset versioning.
Actual Result
I got the below error with the
versioned: true
parameter.Currently, I'm pretty sure that the error comes from my side, I think I missed something.
Your Environment
Include as many relevant details about the environment in which you experienced the bug:
The text was updated successfully, but these errors were encountered: