add ngram tokenizer docs

_analyzers/tokenizers/index.md

@@ -2,7 +2,7 @@
 layout: default
 title: Tokenizers
 nav_order: 60
-has_children: false
+has_children: true
 has_toc: false
 ---
 

_analyzers/tokenizers/ngram.md

@@ -0,0 +1,111 @@
+---
+layout: default
+title: N-gram
+parent: Tokenizers
+nav_order: 80
+---
+
+# N-gram tokenizer
+
+The `ngram` tokenizer splits text into overlapping n-grams (sequences of characters) of a specified length. This tokenizer is particularly useful when you want to perform partial word matching or autocomplete search functionality because it generates substrings (character n-grams) of the original input text.
+
+## Example usage
+
+The following example request creates a new index named `my_index` and configures an analyzer with an `ngram` tokenizer:
+
+```json
+PUT /my_index
+{
+  "settings": {
+    "analysis": {
+      "tokenizer": {
+        "my_ngram_tokenizer": {
+          "type": "ngram",
+          "min_gram": 3,
+          "max_gram": 4,
+          "token_chars": ["letter", "digit"]
+        }
+      },
+      "analyzer": {
+        "my_ngram_analyzer": {
+          "type": "custom",
+          "tokenizer": "my_ngram_tokenizer"
+        }
+      }
+    }
+  }
+}
+```
+{% include copy-curl.html %}
+
+## Generated tokens
+
+Use the following request to examine the tokens generated using the analyzer:
+
+```json
+POST /my_index/_analyze
+{
+  "analyzer": "my_ngram_analyzer",
+  "text": "OpenSearch"
+}
+```
+{% include copy-curl.html %}
+
+The response contains the generated tokens:
+
+```json
+{
+  "tokens": [
+    {"token": "Sea","start_offset": 0,"end_offset": 3,"type": "word","position": 0},
+    {"token": "Sear","start_offset": 0,"end_offset": 4,"type": "word","position": 1},
+    {"token": "ear","start_offset": 1,"end_offset": 4,"type": "word","position": 2},
+    {"token": "earc","start_offset": 1,"end_offset": 5,"type": "word","position": 3},
+    {"token": "arc","start_offset": 2,"end_offset": 5,"type": "word","position": 4},
+    {"token": "arch","start_offset": 2,"end_offset": 6,"type": "word","position": 5},
+    {"token": "rch","start_offset": 3,"end_offset": 6,"type": "word","position": 6}
+  ]
+}
+```
+
+## Parameters
+
+The `ngram` tokenizer can be configured with the following parameters.
+
+Parameter | Required/Optional | Data type | Description
+:--- | :--- | :--- | :--- 
+`min_gram` | Optional | Integer | Minimum length of n-grams. Default is `1`.
+`max_gram` | Optional | Integer | Maximum length of n-grams. Default is `2`.
+`token_chars` | Optional | List of strings | Character classes to be included in tokenization. Valid values are:<br>- `letter`<br>- `digit`<br>- `whitespace`<br>- `punctuation`<br>- `symbol`<br>- `custom` (You must also specify the `custom_token_chars` parameter)<br>Default is empty list (`[]`), which retains all the characters.
+`custom_token_chars` | Optional | String | Custom characters to be included as part of the tokens.
+
+### Maximum difference between `min_gram` and `max_gram`
+
+The maximum difference between `min_gram` and `max_gram` is configured using the index-level `index.max_ngram_diff` setting and defaults to `1`.
+
+The following example creates index with a custom `index.max_ngram_diff` setting: 
+
+```json
+PUT /my-index
+{
+  "settings": {
+    "index.max_ngram_diff": 2, 
+    "analysis": {
+      "tokenizer": {
+        "my_ngram_tokenizer": {
+          "type": "ngram",
+          "min_gram": 3,
+          "max_gram": 5,
+          "token_chars": ["letter", "digit"]
+        }
+      },
+      "analyzer": {
+        "my_ngram_analyzer": {
+          "type": "custom",
+          "tokenizer": "my_ngram_tokenizer"
+        }
+      }
+    }
+  }
+}
+```
+{% include copy-curl.html %}