1 Answer
- Newest
- Most votes
- Most comments
0
Output encoding can be configured by using the CaptureContentTypeHeader in EndpointConfig.DataCaptureConfig. I believe since this is not being set, default encoding i.e. base64 is being used.
Please try once with this attribute set as below:
"CaptureContentTypeHeader": {
"CsvContentTypes": [ "text/csv" ]
}
Assuming that content_type/accept is "text_csv" for the concerned model.
answered a year ago
Thanks this helped
Relevant content
- Accepted Answer
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
This is causing issue while run of analyzer. After baseline is generated and data is captured, when monitoring schedule runs the analyzer it throws error of Encoding mismatch. For it to run EndpointOutput and EndpointInput should have same encoding.
I saw we cannot do anything to change the encoding of output. I used LightGBM, CatBoost algorithms also and found for these EndpointOuput encoding is JSON, which is readable but still not solving the purpose.
Is there a way we can change EndpointOutput Encoding for DataCapture.