You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Motivation:
1) Trying to use json pretty even though it's a string that can't use
json pretty, like json-lines.
2) When copying as a curl command, it uses an array of characters to
insert duplicate semantically identical headers.
Modifications:
1) Trying to use json pretty even though it's a string that can't use
json pretty, like json-lines.
- Fix some mime types to ignore pretty
2) When copying as a curl command, it uses an array of characters to
insert duplicate semantically identical headers.
- Change to `Headers` instead of string array
Result:
- Closes#5218
---------
Co-authored-by: jrhee17 <guins_j@guins.org>
Co-authored-by: minwoox <songmw725@gmail.com>
Discussed in #5214
Originally posted by vthacker September 30, 2023
Hello Armeria folks,
I'm using annotated doc service
@Post("/_bulk")
that can also parse NDJSON strings. This is the only dataformat that Elasticsearch/Opensearch accepts ( https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-bulk.html )The service works as expected, however I am running into an issue with the DocService
I am passing this as my HTTP Headers within the doc service
In the request body if I input NDJSON data, for example
The doc serice parser is complaining since it's expecting data to be JSON
So my first questionn is there a way for me to disable the JSON parsing of the request body?
My second quesion is the DocService dseems to overwrite the content-type header. For example if I change my request body to be a valid JSON
{ "index" : { "_index" : "test", "_id" : "1" } }
and then "Copy as a curl command" I see this
If I change the HTTP Header to be
then I see the request being formed as
The text was updated successfully, but these errors were encountered: