From a432b3e3506a65e448ce745f32f8e8929db56e31 Mon Sep 17 00:00:00 2001 From: Alexander Stehlik Date: Fri, 1 Sep 2023 19:08:44 +0200 Subject: [PATCH] Fix tokenizer config in example The camel cased nGram tokenizer is not allowed any more in Elasticsearch 8.x. Instead the lowercase ngram must be used. See: https://www.elastic.co/guide/en/elasticsearch/reference/current/migrating-8.0.html#nGram-edgeNGram-tokenizer-dreprecation --- .../07_Elastic_Search/01_Configuration_Details.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/05_Index_Service/01_Product_Index_Configuration/07_Elastic_Search/01_Configuration_Details.md b/doc/05_Index_Service/01_Product_Index_Configuration/07_Elastic_Search/01_Configuration_Details.md index a539f3d79..fb9ad4df9 100644 --- a/doc/05_Index_Service/01_Product_Index_Configuration/07_Elastic_Search/01_Configuration_Details.md +++ b/doc/05_Index_Service/01_Product_Index_Configuration/07_Elastic_Search/01_Configuration_Details.md @@ -68,7 +68,7 @@ pimcore_ecommerce_framework: - allow_list_filter tokenizer: my_ngram_tokenizer: - type: nGram + type: ngram min_gram: 2 max_gram: 15 token_chars: [letter, digit]