logstash-filter-mutate 3.5.5 → 3.5.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 53853b61a143395ded602ed7b065eba14dac85d4135b2135c1c0db541062c6a8
-  data.tar.gz: 6a48ec84da666bcc11bef8613f6e8340306c27e39dc4204f2c50cc993c5a2a70
+  metadata.gz: b2e5b32e8796c3dc7709a89d2e345fbd720f4c144dc90150833e357c052473b6
+  data.tar.gz: ce9ac9d9dc6b3ea1e87e3628c6f7a3725aa4defaea47feffbbfbc966824c8113
 SHA512:
-  metadata.gz: f5e4abc14b42d8a8370ed66541c79c27f94a0e26458e70d70c3fb944d4d12f97aeb9d7cb0ad60e6aa2771fe548f473077b9670ab3fdfec4a370654b2624f89ca
-  data.tar.gz: cd46fb549dcefc6b00cc51ca19f17ff19dd6ef86a10d26466a637ed1257ba40e93290a12a1afcca129b980286237fee82203c3b009b6df38e7d4b16fdd446995
+  metadata.gz: 24571cc6195435dc6edfc23cd3c4abae6c6041f77acc5749c5e944ad10f2ed71457b89bbc8c152d836855460ee3b8b0ddbb82139d4b4f1c398f2e9602005161a
+  data.tar.gz: 2be971ad1a39c3e86a6af402c3a08710db26c86fecb7e8a28878bb87ca4e1cb7f72eb7d4290f49079af78252dd3165c17928e0f5d5da7aaf069bf11beb2476f3

data/CHANGELOG.md

@@ -1,12 +1,18 @@
+## 3.5.7
+  - Clarify that `split` and `join` also support strings [#164](https://github.com/logstash-plugins/logstash-filter-mutate/pull/164)
+
+## 3.5.6
+ - [DOC] Added info on maintaining precision between Ruby float and Elasticsearch float [#158](https://github.com/logstash-plugins/logstash-filter-mutate/pull/158)
+
 ## 3.5.5
  - Fix: removed code and documentation for already removed 'remove' option. [#161](https://github.com/logstash-plugins/logstash-filter-mutate/pull/161)
 
 ## 3.5.4
- - DOC: In 'replace' documentation, mention 'add' behavior [#155](https://github.com/logstash-plugins/logstash-filter-mutate/pull/155)
- - DOC: Add warning about #27 [#101](https://github.com/logstash-plugins/logstash-filter-mutate/pull/101)
+ - [DOC] In 'replace' documentation, mention 'add' behavior [#155](https://github.com/logstash-plugins/logstash-filter-mutate/pull/155)
+ - [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)
 
 ## 3.5.3
- - DOC: Expand description and behaviors for `rename` option [#156](https://github.com/logstash-plugins/logstash-filter-mutate/pull/156)
+ - [DOC] Expand description and behaviors for `rename` option [#156](https://github.com/logstash-plugins/logstash-filter-mutate/pull/156)
 
 ## 3.5.2
  - 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 +28,7 @@ the operations are now aborted and a configurable tag is added to the event [#13
  - Added ability to directly convert from integer and float to boolean [#127](https://github.com/logstash-plugins/logstash-filter-mutate/pull/127)
 
 ## 3.3.4
- - Changed documentation to clarify execution order and to provide workaround 
+ - [DOC] Changed documentation to clarify execution order and to provide workaround 
  [#128](https://github.com/logstash-plugins/logstash-filter-mutate/pull/128)
 
 ## 3.3.3

data/docs/index.asciidoc

@@ -100,6 +100,14 @@ Convert a field's value to a different type, like turning a string to an
 integer. If the field value is an array, all members will be converted.
 If the field is a hash no action will be taken.
 
+.Conversion insights
+[NOTE]
+================================================================================
+The values are converted using Ruby semantics.
+Be aware that using `float` and `float_eu` converts the value to a double-precision 64-bit IEEE 754 floating point decimal number.
+In order to maintain precision due to the conversion, you should use a `double` in the Elasticsearch mappings.
+================================================================================
+
 Valid conversion targets, and their expected behaviour with different inputs are:
 
  * `integer`:
@@ -192,7 +200,8 @@ Example:
   * Value type is <<hash,hash>>
   * There is no default value for this setting.
 
-Join an array with a separator character. Does nothing on non-array fields.
+Join an array with a separator character or string.
+Does nothing on non-array fields.
 
 Example:
 [source,ruby]
@@ -304,8 +313,8 @@ Example:
   * Value type is <<hash,hash>>
   * There is no default value for this setting.
 
-Split a field to an array using a separator character. Only works on string
-fields.
+Split a field to an array using a separator character or string.
+Only works on string fields.
 
 Example:
 [source,ruby]

data/logstash-filter-mutate.gemspec

@@ -1,7 +1,7 @@
 Gem::Specification.new do |s|
 
   s.name            = 'logstash-filter-mutate'
-  s.version         = '3.5.5'
+  s.version         = '3.5.7'
   s.licenses        = ['Apache License (2.0)']
   s.summary         = "Performs mutations on fields"
   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

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logstash-filter-mutate
 version: !ruby/object:Gem::Version
-  version: 3.5.5
+  version: 3.5.7
 platform: ruby
 authors:
 - Elastic
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-11-05 00:00:00.000000000 Z
+date: 2023-05-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
@@ -126,7 +126,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.6
+rubygems_version: 3.2.33
 signing_key:
 specification_version: 4
 summary: Performs mutations on fields