-
Notifications
You must be signed in to change notification settings - Fork 472
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into api-template-reconcillation
- Loading branch information
Showing
4 changed files
with
98 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,93 @@ | ||
--- | ||
layout: default | ||
title: Classic | ||
parent: Token filters | ||
nav_order: 50 | ||
--- | ||
|
||
# Classic token filter | ||
|
||
The primary function of the classic token filter is to work alongside the classic tokenizer. It processes tokens by applying the following common transformations, which aid in text analysis and search: | ||
- Removal of possessive endings such as *'s*. For example, *John's* becomes *John*. | ||
- Removal of periods from acronyms. For example, *D.A.R.P.A.* becomes *DARPA*. | ||
|
||
|
||
## Example | ||
|
||
The following example request creates a new index named `custom_classic_filter` and configures an analyzer with the `classic` filter: | ||
|
||
```json | ||
PUT /custom_classic_filter | ||
{ | ||
"settings": { | ||
"analysis": { | ||
"analyzer": { | ||
"custom_classic": { | ||
"type": "custom", | ||
"tokenizer": "classic", | ||
"filter": ["classic"] | ||
} | ||
} | ||
} | ||
} | ||
} | ||
``` | ||
{% include copy-curl.html %} | ||
|
||
## Generated tokens | ||
|
||
Use the following request to examine the tokens generated using the analyzer: | ||
|
||
```json | ||
POST /custom_classic_filter/_analyze | ||
{ | ||
"analyzer": "custom_classic", | ||
"text": "John's co-operate was excellent." | ||
} | ||
``` | ||
{% include copy-curl.html %} | ||
|
||
The response contains the generated tokens: | ||
|
||
```json | ||
{ | ||
"tokens": [ | ||
{ | ||
"token": "John", | ||
"start_offset": 0, | ||
"end_offset": 6, | ||
"type": "<APOSTROPHE>", | ||
"position": 0 | ||
}, | ||
{ | ||
"token": "co", | ||
"start_offset": 7, | ||
"end_offset": 9, | ||
"type": "<ALPHANUM>", | ||
"position": 1 | ||
}, | ||
{ | ||
"token": "operate", | ||
"start_offset": 10, | ||
"end_offset": 17, | ||
"type": "<ALPHANUM>", | ||
"position": 2 | ||
}, | ||
{ | ||
"token": "was", | ||
"start_offset": 18, | ||
"end_offset": 21, | ||
"type": "<ALPHANUM>", | ||
"position": 3 | ||
}, | ||
{ | ||
"token": "excellent", | ||
"start_offset": 22, | ||
"end_offset": 31, | ||
"type": "<ALPHANUM>", | ||
"position": 4 | ||
} | ||
] | ||
} | ||
``` | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters