Set Content-Type and Accept headers #55
Comments
|
Blocked on elastic/elasticsearch-ruby#400 |
|
#56 works around it. |
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Feb 7, 2017
…' header In future, Elasticsearch will require specifying the format of data which is being sent (eg. when indexing a document). Current versions of Elasticsearch will start to print a warning to the deprecation log. A default value 'application/json' for the 'Content-Type' header has been added to prevent the deprecation messages and to be prepared for the requirement in next major version of Elasticsearch. See: elastic/elasticsearch#22691 Related: * c22ec89 * logstash-plugins/logstash-input-elasticsearch#55 * logstash-plugins/logstash-input-elasticsearch#56 * elastic/elasticsearch#22691 Closes #400
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Feb 7, 2017
…' header In future, Elasticsearch will require specifying the format of data which is being sent (eg. when indexing a document). Current versions of Elasticsearch will start to print a warning to the deprecation log. A default value 'application/json' for the 'Content-Type' header has been added to prevent the deprecation messages and to be prepared for the requirement in next major version of Elasticsearch. See: elastic/elasticsearch#22691 Related: * c22ec89 * logstash-plugins/logstash-input-elasticsearch#55 * logstash-plugins/logstash-input-elasticsearch#56 * elastic/elasticsearch#22691 Closes #400
|
Blocking resolved in elastic/elasticsearch-ruby@76f8679 and released as https://rubygems.org/gems/elasticsearch-transport/versions/5.0.2 |
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Feb 7, 2017
…nticore adapter The Manticore adapter doesn't handle the `transport_options` in the same way as the Faraday and Curb adapters. The addition of a default 'Content-Type' header in 76f8679 (#400) didn't work then, and this patch fixes it. Related: * #400 * logstash-plugins/logstash-input-elasticsearch#55 * logstash-plugins/logstash-input-elasticsearch#56
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Feb 7, 2017
…nticore adapter The Manticore adapter doesn't handle the `transport_options` in the same way as the Faraday and Curb adapters. The addition of a default 'Content-Type' header in 76f8679 (#400) didn't work then, and this patch fixes it. Related: * #400 * logstash-plugins/logstash-input-elasticsearch#55 * logstash-plugins/logstash-input-elasticsearch#56
andrewvc
added a commit
to andrewvc/logstash-input-elasticsearch
that referenced
this issue
Feb 7, 2017
Closed
andrewvc
added a commit
to andrewvc/logstash-input-elasticsearch
that referenced
this issue
Feb 7, 2017
|
Version https://rubygems.org/gems/elasticsearch-transport/versions/5.0.3 released, which addresses a bug in the Manticore adapter when handling options. |
andrewvc
added a commit
to andrewvc/logstash-input-elasticsearch
that referenced
this issue
Feb 7, 2017
picandocodigo
pushed a commit
to elastic/elastic-transport-ruby
that referenced
this issue
Jun 7, 2021
…' header In future, Elasticsearch will require specifying the format of data which is being sent (eg. when indexing a document). Current versions of Elasticsearch will start to print a warning to the deprecation log. A default value 'application/json' for the 'Content-Type' header has been added to prevent the deprecation messages and to be prepared for the requirement in next major version of Elasticsearch. See: elastic/elasticsearch#22691 Related: * c22ec891b0be0e3e8f3c10fd7844adfbd2d608ed * logstash-plugins/logstash-input-elasticsearch#55 * logstash-plugins/logstash-input-elasticsearch#56 * elastic/elasticsearch#22691 Closes #400
picandocodigo
pushed a commit
to elastic/elastic-transport-ruby
that referenced
this issue
Jun 7, 2021
…nticore adapter
The Manticore adapter doesn't handle the `transport_options` in the same way
as the Faraday and Curb adapters.
The addition of a default 'Content-Type' header in 76f86793cde0a0e7e816a743c73f69002a53483e
(#400) didn't work then, and this patch fixes it.
Related:
* elastic/elasticsearch-ruby#400
* logstash-plugins/logstash-input-elasticsearch#55
* logstash-plugins/logstash-input-elasticsearch#56
renaperes824
added a commit
to renaperes824/ruby-elastic-transport
that referenced
this issue
Sep 12, 2022
…' header In future, Elasticsearch will require specifying the format of data which is being sent (eg. when indexing a document). Current versions of Elasticsearch will start to print a warning to the deprecation log. A default value 'application/json' for the 'Content-Type' header has been added to prevent the deprecation messages and to be prepared for the requirement in next major version of Elasticsearch. See: elastic/elasticsearch#22691 Related: * c22ec891b0be0e3e8f3c10fd7844adfbd2d608ed * logstash-plugins/logstash-input-elasticsearch#55 * logstash-plugins/logstash-input-elasticsearch#56 * elastic/elasticsearch#22691 Closes #400
renaperes824
added a commit
to renaperes824/ruby-elastic-transport
that referenced
this issue
Sep 12, 2022
…nticore adapter
The Manticore adapter doesn't handle the `transport_options` in the same way
as the Faraday and Curb adapters.
The addition of a default 'Content-Type' header in 76f86793cde0a0e7e816a743c73f69002a53483e
(#400) didn't work then, and this patch fixes it.
Related:
* elastic/elasticsearch-ruby#400
* logstash-plugins/logstash-input-elasticsearch#55
* logstash-plugins/logstash-input-elasticsearch#56
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is necessary to support elastic/elasticsearch#22691 when it lands. Without fixing this, this input will (likely?) not work against new Elasticsearch releases.
The text was updated successfully, but these errors were encountered: