logstash-output-elasticsearch 10.6.1-java → 10.6.2-java

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 712190af3d33e9433c9f6b6dd8efa85406b28e1dddaf344bcaa1c5769708bd44
4
- data.tar.gz: 860e97c8f49c09bb0659939211843cc2799e69feccfb58d4584144a067e6b43f
3
+ metadata.gz: c2b97b57f05641257d4d82abf2ffc924252385a2376e80ed760bef849d5d2699
4
+ data.tar.gz: e4fd909cb0fbe096ff54abc0f77c013e601c7a4c01e3ba3bc72a7e121739a80e
5
5
  SHA512:
6
- metadata.gz: 2aa2d08a6bdf2248091afb58fe46d79f5144a07ff2512aa6ba3511242037da6577cefae0e0da7278bab13e1382abda215dee081154eec79d75604f8f4a054386
7
- data.tar.gz: ebeb646959ce0baf384036dfd34c035a13f88deded066d9557c3d13770dfeb37a241385ab4612f702a4e850fb835903cddc81ed28445e799a2f9d8ce81b50e0c
6
+ metadata.gz: a17060e61a967293beda8046c0bc03d8583049509f0434c07c6024873b166a6cc2a011a6fa6293daee18f7fef6b6ca5f562e37c61f3150684ac88e58a397384b
7
+ data.tar.gz: f9f660a1b5d5eecb4a80dcafbd52872b34b4491a3d3b62e57d3710961c771488368960ec1662c5c2503de1ce2da45fc2b39f0900f407ed8f304b28539c291c26
@@ -1,8 +1,12 @@
1
+ ## 10.6.2
2
+ - [DOC] Added clarifying info on http compression settings and behaviors [#943](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/943)
3
+ - [DOC] Fixed entry for ilm_policy default value[#956](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/956)
4
+
1
5
  ## 10.6.1
2
6
  - Fixed an issue introduced in 10.6.0 that broke Logstash Core's monitoring feature when this plugin is run in Logstash 7.7-7.8. [#953](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/953)
3
7
 
4
8
  ## 10.6.0
5
- - Added `ecs_compatiblity` mode, for managing ECS-compatable templates [#952](https://github.com/logstash-plugins/logstash-output-elasticsearch/issue/952)
9
+ - Added `ecs_compatiblity` mode, for managing ECS-compatable templates [#952](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/952)
6
10
 
7
11
  ## 10.5.1
8
12
  - [DOC] Removed outdated compatibility notices, reworked cloud notice, and fixed formatting for `hosts` examples [#938](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/938)
@@ -218,13 +218,17 @@ not reevaluate its DNS value while the keepalive is in effect.
218
218
 
219
219
  ==== HTTP Compression
220
220
 
221
- This plugin supports request and response compression. Response compression is enabled by default and
222
- for Elasticsearch versions 5.0 and later, the user doesn't have to set any configs in Elasticsearch for
223
- it to send back compressed response. For versions before 5.0, `http.compression` must be set to `true` https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html#modules-http[in
224
- Elasticsearch] to take advantage of response compression when using this plugin
221
+ This plugin supports request and response compression. Response compression is
222
+ enabled by default for HTTP and for Elasticsearch versions 5.0 and later.
225
223
 
226
- For requests compression, regardless of the Elasticsearch version, users have to enable `http_compression`
227
- setting in their Logstash config file.
224
+ You don't have to set any configs in Elasticsearch for it to send back a
225
+ compressed response. For versions before 5.0, or if HTTPS is enabled,
226
+ `http.compression` must be set to `true`
227
+ https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html#modules-http[in
228
+ Elasticsearch] to take advantage of response compression when using this plugin.
229
+
230
+ For requests compression, regardless of the Elasticsearch version, enable the
231
+ `http_compression` setting in the Logstash config file.
228
232
 
229
233
  ==== Authentication
230
234
 
@@ -523,7 +527,7 @@ NOTE: The pattern must finish with a dash and a number that will be automaticall
523
527
  ===== `ilm_policy`
524
528
 
525
529
  * Value type is <<string,string>>
526
- * Default value is `logstash`
530
+ * Default value is `logstash-policy`
527
531
 
528
532
  Modify this setting to use a custom Index Lifecycle Management policy, rather than the default. If this value is not set, the default policy will
529
533
  be automatically installed into Elasticsearch
@@ -1,6 +1,6 @@
1
1
  Gem::Specification.new do |s|
2
2
  s.name = 'logstash-output-elasticsearch'
3
- s.version = '10.6.1'
3
+ s.version = '10.6.2'
4
4
 
5
5
  s.licenses = ['apache-2.0']
6
6
  s.summary = "Stores logs in Elasticsearch"
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: logstash-output-elasticsearch
3
3
  version: !ruby/object:Gem::Version
4
- version: 10.6.1
4
+ version: 10.6.2
5
5
  platform: java
6
6
  authors:
7
7
  - Elastic
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2020-07-15 00:00:00.000000000 Z
11
+ date: 2020-08-04 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  requirement: !ruby/object:Gem::Requirement