HTTP JSON API - 2 Responses for a single request

[DiegoAlfa7]

HTTP JSON API - 2 Responses for a single request

[Nick-S-2018]

In your gist example, payload data passed to the request does not match the required format. You can see info about the use of /bulk here: https://manual.manticoresearch.com/dev/Data_creation_and_modification/Adding_documents_to_a_table/Adding_documents_to_a_real-time_table#Bulk-adding-documents

[DiegoAlfa7]

I've updated the bug script, forget the gist.

Heres a screenshot that shows the bug when executing the script and ngreping the API port:

[Nick-S-2018]

Hi,
It appears the request from the updated script still has a few errors:

• the PAYLOAD data you encode already has encoded unicode sequences which leads to double encoding and an error when Manticore tries to decode it, so the request needs unicode-decoding as well (something like PAYLOAD.encode('utf-8').decode('unicode-escape') should help)
• the data contains null values, unvalid in the JSON schema
• some fields are undefined in your table schema, but present in the data, e.g., sentiment
• the feeds field is defined as multi64, but string values are passed for it in the data which is not allowed in Manticore
• the id field passed twice for each data row, as a separate field and as a field in the doc object, which cannot be correctly handled by Manticore (also, take note that the document id must be a number, not a string)

Can you please fix them and repeat your tests?

[DiegoAlfa7]

Im into it, anyway, if the payload contains such errors (wich are definetly not supposed to be there) shouldn't manticore respond only one time with the corresponding 400 / 500 Response code?

I mean, the issue in the MRE is still on our side, but seems odd that the API responds 200 - OK to python requests, that could (an did, in my case) lead to silent errors and unexpected missing data.

Im still convinced that the issue has something to do with the unicode chars. I will solve all issues except for that one in a specific test and then i will test it again with the payload encoded in utf8 and show you both results.

Sorry for the issues with the MRE.
Thanks for your time.