mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-29 01:44:36 -04:00
* [docs] Prepare for docs-assembler (#125118)
* reorg files for docs-assembler and create toc.yml files
* fix build error, add redirects
* only toc
* move images
(cherry picked from commit 9bcd59596d
)
# Conflicts:
# docs/reference/aggregations/search-aggregations-pipeline-bucket-script-aggregation.md
# docs/reference/aggregations/search-aggregations-pipeline-cumulative-cardinality-aggregation.md
# docs/reference/aggregations/search-aggregations-pipeline-cumulative-sum-aggregation.md
# docs/reference/aggregations/search-aggregations-pipeline-derivative-aggregation.md
# docs/reference/aggregations/search-aggregations-pipeline-extended-stats-bucket-aggregation.md
# docs/reference/aggregations/search-aggregations-pipeline-max-bucket-aggregation.md
# docs/reference/aggregations/search-aggregations-pipeline-min-bucket-aggregation.md
# docs/reference/aggregations/search-aggregations-pipeline-percentiles-bucket-aggregation.md
# docs/reference/aggregations/search-aggregations-pipeline-stats-bucket-aggregation.md
# docs/reference/aggregations/search-aggregations-pipeline-sum-bucket-aggregation.md
# docs/reference/query-languages/esql/esql-commands.md
# docs/reference/query-languages/esql/esql-lookup-join.md
# docs/reference/query-languages/esql/esql-process-data-with-dissect-grok.md
# docs/reference/query-languages/images/esql-lookup-join.png
# docs/reference/query-languages/toc.yml
# docs/reference/search-connectors/es-connectors-run-from-docker.md
# docs/reference/text-analysis/analysis-apostrophe-tokenfilter.md
# docs/reference/toc.yml
* remove markers
---------
Co-authored-by: Colleen McGinnis <colleen.mcginnis@elastic.co>
2.3 KiB
2.3 KiB
navigation_title | mapped_pages | |
---|---|---|
Split |
|
Split processor [split-processor]
Splits a field into an array using a separator character. Only works on string fields.
$$$split-options$
Name | Required | Default | Description |
---|---|---|---|
field |
yes | - | The field to split |
separator |
yes | - | A regex which matches the separator, eg , or \s+ |
target_field |
no | field |
The field to assign the split value to, by default field is updated in-place |
ignore_missing |
no | false |
If true and field does not exist, the processor quietly exits without modifying the document |
preserve_trailing |
no | false |
Preserves empty trailing fields, if any. |
description |
no | - | Description of the processor. Useful for describing the purpose of the processor or its configuration. |
if |
no | - | Conditionally execute the processor. See Conditionally run a processor. |
ignore_failure |
no | false |
Ignore failures for the processor. See Handling pipeline failures. |
on_failure |
no | - | Handle failures for the processor. See Handling pipeline failures. |
tag |
no | - | Identifier for the processor. Useful for debugging and metrics. |
{
"split": {
"field": "my_field",
"separator": "\\s+" <1>
}
}
- Treat all consecutive whitespace characters as a single separator
If the preserve_trailing
option is enabled, any trailing empty fields in the input will be preserved. For example, in the configuration below, a value of A,,B,,
in the my_field
property will be split into an array of five elements ["A", "", "B", "", ""]
with two empty trailing fields. If the preserve_trailing
property were not enabled, the two empty trailing fields would be discarded resulting in the three-element array ["A", "", "B"]
.
{
"split": {
"field": "my_field",
"separator": ",",
"preserve_trailing": true
}
}