-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Improve docs and tests for convert processor
#133160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 10 commits
e7c3bac
3de1ec3
753e77d
9076d9d
1d89527
eaa39b3
49996aa
51d63db
7ec8b13
a591de8
4f4ff85
899f34f
061cedf
a603cb4
466ba40
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,16 +6,36 @@ mapped_pages: | |
|
|
||
| # Convert processor [convert-processor] | ||
|
|
||
|
|
||
| Converts a field in the currently ingested document to a different type, such as converting a string to an integer. If the field value is an array, all members will be converted. | ||
|
|
||
| The supported types include: `integer`, `long`, `float`, `double`, `string`, `boolean`, `ip`, and `auto`. | ||
| The supported types are: `integer`, `long`, `float`, `double`, `string`, `boolean`, `ip`, and `auto`. | ||
|
|
||
| | Target `type` | Supported input values | | ||
| |---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | `integer` | `Integer` values<br><br>`Long` values in 32-bit signed integer range<br><br>`String` values representing an integer in 32-bit signed integer range in either decimal format (without a decimal point) or hex format (e.g. `"123"` or `"0x7b"`) | | ||
| | `long` | `Integer` values<br><br>`Long` values<br><br>`String` values representing an integer in 64-bit signed integer range in either decimal format (without a decimal point) or hex format (e.g. `"123"` or `"0x7b"`) | | ||
| | `float` | `Integer` values (may lose precision for absolute values greater than 2^24)<br><br>`Long` values (may lose precision for absolute values greater than 2^24)<br><br>`Float` values<br><br>`Double` values (may lose precision)<br><br>`String` values representing a floating point number in decimal, scientific, or hex format (e.g. `"123.0"`, `"123.45"`, `"1.23e2"`, or `"0x1.ecp6"`) or an integer (may lose precision, and will give positive or negative infinity if out of range for a 32-bit floating point value) | | ||
|
||
| | `double` | `Integer` values<br><br>`Long` values (may lose precision for absolute values greater than 2^53)<br><br>`Float` values<br><br>`Double` values<br><br>`String` values representing a floating point number in decimal, scientific, or hex format (e.g. `"123.0"`, `"123.45"`, `"1.23e2"`, or `"0x1.ecp6"`) or an integer (may lose precision, and will give positive or negative infinity if out of range for a 64-bit floating point value) | | ||
| | `string` | All values | | ||
| | `boolean` | `Boolean` values<br><br>`String` values matching `"true"` or `"false"` (case insensitive) | | ||
| | `ip` | `String` values containing a valid IPv4 or IPv6 address that can be indexed into an [IP field type](/reference/elasticsearch/mapping-reference/ip.md) | | ||
| | `auto` | All values (see below) | | ||
|
|
||
| Specifying `auto` will attempt to convert a string-valued `field` into the closest non-string, non-IP type: | ||
| - A whose value is `"true"` or `"false"` (case insensitive) will be converted to a `Boolean`. | ||
| - A string representing an integer in decimal or hex format (e.g. `"123"` or `"0x7b"`) will be converted to an `Integer` if the number fits in a 32-bit signed integer, else to a `Long` if it fits in a 64-bit signed integer, else to a `Float` (in which case it may | ||
| lose precision, and will give positive or negative infinity if out of range for a 32-bit floating point value). | ||
| - A string representing a floating point number in decimal, scientific, or hex format (e.g. `"123.0"`, `"123.45"`, `"1.23e2"`, or `"0x1.ecp6"`) will be converted to a `Float` (and may lose precision, and will give positive or negative infinity if out of range for a 32-bit floating point value). | ||
|
|
||
| Specifying `boolean` will set the field to true if its string value is equal to `true` (ignore case), to false if its string value is equal to `false` (ignore case), or it will throw an exception otherwise. | ||
| Using `auto` to convert a `field` which is either not a `String` or a `String` which cannot be will leave the field | ||
| value as-is. In such a case, `target_field` will be updated with the unconverted field value. | ||
|
|
||
| Specifying `ip` will set the target field to the value of `field` if it contains a valid IPv4 or IPv6 address that can be indexed into an [IP field type](/reference/elasticsearch/mapping-reference/ip.md). | ||
| :::{tip} | ||
| If conversions other than those provided by this processor are required, the | ||
| [`script`](/reference/enrich-processor/script-processor.md) processor may be used to implement the desired behavior. | ||
|
|
||
| Specifying `auto` will attempt to convert the string-valued `field` into the closest non-string, non-IP type. For example, a field whose value is `"true"` will be converted to its respective boolean type: `true`. Do note that float takes precedence of double in `auto`. A value of `"242.15"` will "automatically" be converted to `242.15` of type `float`. If a provided field cannot be appropriately converted, the processor will still process successfully and leave the field value as-is. In such a case, `target_field` will be updated with the unconverted field value. | ||
| The performance of the `script` processor should be as good or better than the `convert` processor. | ||
| ::: | ||
|
|
||
| $$$convert-options$$$ | ||
PeteGillinElastic marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
|
|
||

Uh oh!
There was an error while loading. Please reload this page.