-
Notifications
You must be signed in to change notification settings - Fork 834
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
transform_output_raw not working . It gets refered to transform-input endpoint when analysing logs #2277
Comments
Hi @divyadilip91, please fill out the template for bug creations in seldon, so we know exactly what image you used to wrap your model vs the image of the service orchestrator, as well as the yaml so we can reproduce. Thanks |
Hi @axsaucedo |
@axsaucedo @RafalSkolasinski Hi . I am facing issue in creating the seldon graph too.. I am using seldon v1.1.0. |
This can be achieved by making your model3 an output-transformer so it runs after the combiner. |
Hi @cliveseldon |
Please try setting |
@RafalSkolasinski Thanks for your reply. So only an output transformer can be a parent of combiner?Could I connect the output from a combiner to be passed as input to another model/input transformer? |
As far as I am aware only the In other words, parents of The difference of For the diagram above you could try: - name: output-transformer
type: OUTPUT_TRANSFORMER
children:
- name: model-3
type: OUTPUT_TRANSFORMER
children:
- name: combiner
type: COMBINER
children:
- name: model-1
type: MODEL
- name: model-2
type: MODEL |
@divyadilip91 Ok got it. Thankyou for your response. |
Hi,
I found an issue with transform_output_raw which did not seem to be working. I created a graph with a model and an output transformer and found that the ouptut from model (using predict_raw) was not passed to the transformer and in the logs I could see that "/transform-input" endpoint is being called instead of /transform-output
The seldon version I am using is 1.1.0.
Has this been fixed in the higher versions?
Expecting your reply
The text was updated successfully, but these errors were encountered: