mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 17:34:17 -04:00
* delete asciidoc files
* add migrated files
* fix errors
* Disable docs tests
* Clarify release notes page titles
* Revert "Clarify release notes page titles"
This reverts commit 8be688648d
.
* Comment out edternal URI images
* Clean up query languages landing pages, link to conceptual docs
* Add .md to url
* Fixes inference processor nesting.
---------
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
Co-authored-by: Liam Thompson <leemthompo@gmail.com>
Co-authored-by: Martijn Laarman <Mpdreamz@gmail.com>
Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>
1.4 KiB
1.4 KiB
navigation_title | mapped_pages | |
---|---|---|
Whitespace |
|
Whitespace analyzer [analysis-whitespace-analyzer]
The whitespace
analyzer breaks text into terms whenever it encounters a whitespace character.
Example output [_example_output_6]
POST _analyze
{
"analyzer": "whitespace",
"text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
}
The above sentence would produce the following terms:
[ The, 2, QUICK, Brown-Foxes, jumped, over, the, lazy, dog's, bone. ]
Configuration [_configuration_7]
The whitespace
analyzer is not configurable.
Definition [_definition_6]
It consists of:
- Tokenizer
If you need to customize the whitespace
analyzer then you need to recreate it as a custom
analyzer and modify it, usually by adding token filters. This would recreate the built-in whitespace
analyzer and you can use it as a starting point for further customization:
PUT /whitespace_example
{
"settings": {
"analysis": {
"analyzer": {
"rebuilt_whitespace": {
"tokenizer": "whitespace",
"filter": [ <1>
]
}
}
}
}
}
- You’d add any token filters here.