-
Notifications
You must be signed in to change notification settings - Fork 835
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
Seldon component exit on failure without passing to next component in the seldon graph #2730
Comments
If you return an exception or non-200 it should fail immediatly |
Hi @cliveseldon , Is this possible only if I use the seldon UserCustomException for handling exceptions?
I find that the error is returned to the second component rather than exiting from the first component. |
yes - as in above you would be a 200 OK result returned. |
Ok..so if I want to exit from the first component , I need to use the seldon user custom exception ? |
Yes |
You can also have a router after the first model and return -2 see https://docs.seldon.io/projects/seldon-core/en/latest/analytics/routers.html |
Closing. Please reopen if still an issue. |
Hi team,
My current scenario uses a seldon graph containing two components chained together - that is 2 models.
INPUT----> MODEL1------> MODEL2------> OUTPUT.
I have included error handling in the code for both components.
So my query is, if model1 fails ,can it return the error directly to the user after exiting the seldon graph rather than passing the error to the model2 which will inturn return the error of model2 to the user which is wrong coz the main error that occured was in model1 and the user should see the error message of model1 rather than model2.
Kindly help if there is some solution existing to solve this.
The text was updated successfully, but these errors were encountered: