-
Notifications
You must be signed in to change notification settings - Fork 905
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
ThreadRunner Dataset DatasetAlreadyExistsError: Dataset has already been registered #4250
Comments
We discussed this in private, the conclusion is that it's exactly the same issue users report before. #4093 attempts to fix this, but it only fix the path where user start a KedroSession, i.e. We agreed the temporary fix should goes into |
Based on the solution proposed for lazy loading #3935 (comment) we suggest moving the warm-up to the Line 115 in a5d9bb4
Further, we replace this logic with lazy loading warm-up which will be common for all the runners as well. |
Solved in #4262 |
Description
Originated from #4210
Context
Upon investigation, I found that this error seems to be related to dataset factory pattern only.
The current conclusion is that this is not an error introduced recently. Though there seems to be partial fix previously but it doesn't works for my test case.
Related:
Steps to Reproduce
Using a similar test written in #4210 from
benchmark_runner.py
for ThreadRunner.This is the snippet that I use:
Run this multiple times to confirm it fails (non-deterministic fail due to race condition). Then uncomment the
dummy_x
dataset to pre-register it, now it always pass.Expected Result
Actual Result
Your Environment
pip show kedro
orkedro -V
):python -V
):The text was updated successfully, but these errors were encountered: