logstash-filter-mutate 3.5.5 → 3.5.6
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +7 -4
- data/docs/index.asciidoc +8 -0
- data/logstash-filter-mutate.gemspec +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: e7bbcb6c1b884bd1f9c2653e0c42b5cf4df89861e8d73c80375e6b6ce002e7ba
|
4
|
+
data.tar.gz: f069158a723bce0e79a3ff832703d7c55c773c48b7a57b7b87466e8f980a3f84
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: b0efa47627024ab7246ac3dbea389665b5802394cd5c5239370014ff6e60b538c2c61a5240ab5774ccebe21b2662bc8b2540fe43adf3131303a5c0b3bad84be5
|
7
|
+
data.tar.gz: c6f2c51923fe115eaa2d35b3b1b325c0d018f784fe7ed6455f600c61e937b4e3f166a2a2eadff1b126c6b73de9f88b9637621ca175d8767beee9e7a519ff1d4b
|
data/CHANGELOG.md
CHANGED
@@ -1,12 +1,15 @@
|
|
1
|
+
## 3.5.6
|
2
|
+
- [DOC] Added info on maintaining precision between Ruby float and Elasticsearch float [#158](https://github.com/logstash-plugins/logstash-filter-mutate/pull/158)
|
3
|
+
|
1
4
|
## 3.5.5
|
2
5
|
- Fix: removed code and documentation for already removed 'remove' option. [#161](https://github.com/logstash-plugins/logstash-filter-mutate/pull/161)
|
3
6
|
|
4
7
|
## 3.5.4
|
5
|
-
- DOC
|
6
|
-
- DOC
|
8
|
+
- [DOC] In 'replace' documentation, mention 'add' behavior [#155](https://github.com/logstash-plugins/logstash-filter-mutate/pull/155)
|
9
|
+
- [DOC] Note that each mutate must be in its own code block as noted in issue [#27](https://github.com/logstash-plugins/logstash-filter-mutate/issues/27). Doc fix [#101](https://github.com/logstash-plugins/logstash-filter-mutate/pull/101)
|
7
10
|
|
8
11
|
## 3.5.3
|
9
|
-
- DOC
|
12
|
+
- [DOC] Expand description and behaviors for `rename` option [#156](https://github.com/logstash-plugins/logstash-filter-mutate/pull/156)
|
10
13
|
|
11
14
|
## 3.5.2
|
12
15
|
- Fix: ensure that when an error occurs during registration, we use the correct i18n key to propagate the error message in a useful manner [#154](https://github.com/logstash-plugins/logstash-filter-mutate/pull/154)
|
@@ -22,7 +25,7 @@ the operations are now aborted and a configurable tag is added to the event [#13
|
|
22
25
|
- Added ability to directly convert from integer and float to boolean [#127](https://github.com/logstash-plugins/logstash-filter-mutate/pull/127)
|
23
26
|
|
24
27
|
## 3.3.4
|
25
|
-
- Changed documentation to clarify execution order and to provide workaround
|
28
|
+
- [DOC] Changed documentation to clarify execution order and to provide workaround
|
26
29
|
[#128](https://github.com/logstash-plugins/logstash-filter-mutate/pull/128)
|
27
30
|
|
28
31
|
## 3.3.3
|
data/docs/index.asciidoc
CHANGED
@@ -100,6 +100,14 @@ Convert a field's value to a different type, like turning a string to an
|
|
100
100
|
integer. If the field value is an array, all members will be converted.
|
101
101
|
If the field is a hash no action will be taken.
|
102
102
|
|
103
|
+
.Conversion insights
|
104
|
+
[NOTE]
|
105
|
+
================================================================================
|
106
|
+
The values are converted using Ruby semantics.
|
107
|
+
Be aware that using `float` and `float_eu` converts the value to a double-precision 64-bit IEEE 754 floating point decimal number.
|
108
|
+
In order to maintain precision due to the conversion, you should use a `double` in the Elasticsearch mappings.
|
109
|
+
================================================================================
|
110
|
+
|
103
111
|
Valid conversion targets, and their expected behaviour with different inputs are:
|
104
112
|
|
105
113
|
* `integer`:
|
@@ -1,7 +1,7 @@
|
|
1
1
|
Gem::Specification.new do |s|
|
2
2
|
|
3
3
|
s.name = 'logstash-filter-mutate'
|
4
|
-
s.version = '3.5.
|
4
|
+
s.version = '3.5.6'
|
5
5
|
s.licenses = ['Apache License (2.0)']
|
6
6
|
s.summary = "Performs mutations on fields"
|
7
7
|
s.description = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program"
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: logstash-filter-mutate
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 3.5.
|
4
|
+
version: 3.5.6
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Elastic
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2021-
|
11
|
+
date: 2021-12-02 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|