Skip to content
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

Add support for transformers with arbitrary request/response format (ie. not SeldonMessage) #3096

Closed
mlegore opened this issue Mar 26, 2021 · 2 comments
Labels
triage Needs to be triaged and prioritised accordingly

Comments

@mlegore
Copy link

mlegore commented Mar 26, 2021

One feature I have been looking for in Seldon is the ability to pre-process requests of formats that don't comply with SeldonMessage. This would be useful for glueing together systems that don't know they're calling seldon.

For example, I'd like to set up a model to be called from a Google Pub/Sub message, but the json message that is sent by Pub/Sub is not in the format of a SeldonMessage, so right now I would have to set up another worker component (a cloud function or similar) to translate the message into a SeldonMessage before calling Seldon. It would be useful if seldon could include that in its routing graph and keep more of the logic contained within Seldon.

@mlegore mlegore added the triage Needs to be triaged and prioritised accordingly label Mar 26, 2021
@axsaucedo
Copy link
Contributor

@mlegore although not exlplicitly documented it is currently possible to send arbitrary payloads to the API, and process them using predict_raw, or in your case transform_input_raw. We currently have #2497 to explore this, so closing this issue.

@mlegore
Copy link
Author

mlegore commented Apr 15, 2021

@axsaucedo is there some examples or documentation for this, in particular how to do this with a language other than python?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs to be triaged and prioritised accordingly
Projects
None yet
Development

No branches or pull requests

2 participants