-
Notifications
You must be signed in to change notification settings - Fork 101
how to handle application/x-image ? #138
Comments
It is not a supported by default content type. Could you share a link to the official documentation you are referring to, so we could clarify it? |
sorry for the delayed response here. in the links you provided, I'm seeing "application/x-image" only as an example. documentation for supported content types: https://github.com/aws/sagemaker-tensorflow-serving-container/blob/master/README.md#prepost-processing |
@laurenyu I would suggest adding an explicit comment, that 'application/x-image' is not supported by default. |
@kafka399 thanks for the suggestion! I'm no longer a maintainer of this repository, so I probably won't get to this particularly soon - feel free to submit a PR yourself if you'd like. cc @ChuyangDeng |
What about the example for It says:
Is this obsolete? |
Here is another example showing that one can send People might really think it should work from all these examples, but it doesn't. |
Can we get clarity on this? if this is not supported why are there examples on aws docs using |
In a transform job, you can use (I checked the code worked with boto3==1.26.31 and sagemaker==2.124.0 .)
You can include your Please remember that your custom handlers can handle the content type as follows.
Maybe I'm too late, but I hope this will help you. |
Im getting:
Its documented in official documentation:
How to get rid of this error ?
The text was updated successfully, but these errors were encountered: