-
Notifications
You must be signed in to change notification settings - Fork 831
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
Executor does not send feedback to Routers. #2827
Comments
In this case it would skip calling the ROUTER component in favour of getting it from the meta (
send_feedback instead of predict , so it should still pass the feedback to the router MODEL nodes.
Do you mean that currently it's not passing the data to the |
For MABs there is logic in send-feedback to update state so I think it should send feedback to routers. |
Oh I see what you mean, so basically it shouldn't call the "route" method, but it should still call the send_feedback method. Ok I can see that the MAB router also has a send_feedback logic, so it would make sense. It seems that also adding the
It seems that the predictor bean also has similar logic: seldon-core/engine/src/main/java/io/seldon/engine/predictors/PredictiveUnitBean.java Line 300 in 23d7dc5
I'm not as familiar with the java side, so just to confirm, is this assumption correct? I do agree that it would make sense to also ensure the send_feedback is passed to the router element, as it could help update its current state. Do you think it should be done explicitly by providing the |
Yes. That makes sense. The logic is in the engine but missing from the executor. |
https://github.com/SeldonIO/seldon-core/blob/master/executor/predictor/predictor_process.go#L135
The text was updated successfully, but these errors were encountered: