-
Notifications
You must be signed in to change notification settings - Fork 473
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Anton Rubin <[email protected]>
- Loading branch information
1 parent
76486a4
commit e9d1faa
Showing
2 changed files
with
103 additions
and
1 deletion.
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,102 @@ | ||
--- | ||
layout: default | ||
title: Unique | ||
parent: Token filters | ||
nav_order: 450 | ||
--- | ||
|
||
# Unique token filter | ||
|
||
The `unique` token filter ensures that only unique tokens are kept during the analysis process, removing duplicate tokens that appear within a single field or text block. | ||
|
||
## Parameters | ||
|
||
The `unique` token filter can be configured with `only_on_same_position` parameter. If set to `true`, this token filter will act as `remove_duplicates` token filter and will only remove tokens that are in the same position. | ||
|
||
## Example | ||
|
||
The following example request creates a new index named `unique_example` and configures an analyzer with `unique` filter: | ||
|
||
```json | ||
PUT /unique_example | ||
{ | ||
"settings": { | ||
"analysis": { | ||
"filter": { | ||
"unique_filter": { | ||
"type": "unique", | ||
"only_on_same_position": false | ||
} | ||
}, | ||
"analyzer": { | ||
"unique_analyzer": { | ||
"type": "custom", | ||
"tokenizer": "standard", | ||
"filter": [ | ||
"lowercase", | ||
"unique_filter" | ||
] | ||
} | ||
} | ||
} | ||
} | ||
} | ||
``` | ||
{% include copy-curl.html %} | ||
|
||
## Generated tokens | ||
|
||
Use the following request to examine the tokens generated using the analyzer: | ||
|
||
```json | ||
GET /unique_example/_analyze | ||
{ | ||
"analyzer": "unique_analyzer", | ||
"text": "OpenSearch OpenSearch is powerful powerful and scalable" | ||
} | ||
``` | ||
{% include copy-curl.html %} | ||
|
||
The response contains the generated tokens: | ||
|
||
```json | ||
{ | ||
"tokens": [ | ||
{ | ||
"token": "opensearch", | ||
"start_offset": 0, | ||
"end_offset": 10, | ||
"type": "<ALPHANUM>", | ||
"position": 0 | ||
}, | ||
{ | ||
"token": "is", | ||
"start_offset": 22, | ||
"end_offset": 24, | ||
"type": "<ALPHANUM>", | ||
"position": 1 | ||
}, | ||
{ | ||
"token": "powerful", | ||
"start_offset": 25, | ||
"end_offset": 33, | ||
"type": "<ALPHANUM>", | ||
"position": 2 | ||
}, | ||
{ | ||
"token": "and", | ||
"start_offset": 43, | ||
"end_offset": 46, | ||
"type": "<ALPHANUM>", | ||
"position": 3 | ||
}, | ||
{ | ||
"token": "scalable", | ||
"start_offset": 47, | ||
"end_offset": 55, | ||
"type": "<ALPHANUM>", | ||
"position": 4 | ||
} | ||
] | ||
} | ||
``` |