Include 'Content-Type' header in transport_options
#250
Conversation
Starting with Elasticsearch 5.3, rest requests without an explicit Content-Type are deprecated and it'll log a warning for every request that is sent without a Content-Type header. I addressed this in a similar manner to how `elasticsearch-ruby` did, see [1], [2]. [1]: elastic/elasticsearch-ruby#400 [2]: elastic/elasticsearch-ruby@76f8679
1 similar comment
|
👍 I'm seeing lots of logs complaining about this on my ES cluster. This would be very welcomed |
|
Would be great to see this merged 👍 @pitr @repeatedly @gihad could we please get some clarification on who is the active maintainer, discussion on #240 suggests we don't currently have one? |
|
@Tom-Fawcett That's correct, we currently don't have the bandwidth within Uken to actively maintain this repo but we can keep it open sourced and hopefully we will be able to spend more time on it soon. Having said that I merged your changed and bumped the plugin version. |
|
@gihad thanks for clarifying, and merging; much appreciated! Regarding maintance - have you read @repeatedly 's comments on #240 regarding possible help? |
|
Thanks for the suggestion. I will reach out to him. |
Starting with Elasticsearch 5.3, (REST) requests without an explicit Content-Type are deprecated and Elasticsearch will log a warning for every request that is sent without a Content-Type header.
I addressed this in a similar manner to how
elasticsearch-rubydid, see 1, 2.(check all that apply)
versionin gemspec are untouchedelasticsearch_dynamic(not required but recommended)