-
Notifications
You must be signed in to change notification settings - Fork 909
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
kedro tries to instantiate DataSet '_sql' that is used for YAML factorization #2363
Comments
Hi @edwardcjohnson this looks like a bug - downgrade to 0.18.4 for now and we'll look into it on our end |
thank you @datajoely |
Hi @edwardcjohnson, could you confirm which config loader you were using in your project? I'm able to reproduce this error with |
to reproduce the issue, i used |
Thanks for reporting this @edwardcjohnson! I'll close this issue but this feature is on the agenda for |
Thanks @ankatiyar! |
Description
Hello, i upgraded from 0.18.2 to 0.18.5 and now get an error with a section of my catalog that leverages the YAML factorization capability (ref https://kedro.readthedocs.io/en/stable/data/data_catalog.html#load-multiple-datasets-with-similar-configuration) with pandas.SQLQueryDataSet.
It seems that kedro 0.18.5 is now trying to instantiate my factorized YAML despite the prefix "_" i am using with "_sql" as mentioned in the docs:
"It’s important that the name of the template entry starts with a _ so Kedro knows not to try and instantiate it as a dataset."
Context
I can easily work around the bug by not using the factorization capability, but of course this means i have to copy+paste the same lines of code multiple times in my catalog.yml
Note that i have only checked this for
pandas.SQLQueryDataSet
.Steps to Reproduce
my_test_sql_query
dataset in a kedro pipelineExpected Result
The pipeline should complete without error when it uses the referenced catalog dataset
Actual Result
Error message that stops the pipeline run
Your Environment
Include as many relevant details about the environment in which you experienced the bug:
pip show kedro
orkedro -V
): kedro, version 0.18.5python -V
): Python 3.9.12The text was updated successfully, but these errors were encountered: