From eab19b56daae5e1eb663e66773ada9e70523ee1c Mon Sep 17 00:00:00 2001 From: Mayya Sharipova Date: Mon, 1 May 2023 05:32:38 -0400 Subject: [PATCH] Clarify path_hierarchy documentation (#44910) * Resolve merge conflicts and apply review suggestions * Fix URLs --------- Co-authored-by: Abdon Pijpelink --- .../analysis/tokenizers/pathhierarchy-tokenizer.asciidoc | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/reference/analysis/tokenizers/pathhierarchy-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/pathhierarchy-tokenizer.asciidoc index 293ee15d8f45..2cf01b77d57a 100644 --- a/docs/reference/analysis/tokenizers/pathhierarchy-tokenizer.asciidoc +++ b/docs/reference/analysis/tokenizers/pathhierarchy-tokenizer.asciidoc @@ -6,7 +6,9 @@ The `path_hierarchy` tokenizer takes a hierarchical value like a filesystem path, splits on the path separator, and emits a term for each component in the -tree. +tree. The `path_hierarcy` tokenizer uses Lucene's +https://lucene.apache.org/core/{lucene_version_path}/analysis/common/org/apache/lucene/analysis/path/PathHierarchyTokenizer.html[PathHierarchyTokenizer] +underneath. [discrete] === Example output @@ -81,7 +83,9 @@ The `path_hierarchy` tokenizer accepts the following parameters: text has been consumed. It is advisable not to change this setting. `reverse`:: - If set to `true`, emits the tokens in reverse order. Defaults to `false`. + If `true`, uses Lucene's + http://lucene.apache.org/core/{lucene_version_path}/analysis/common/org/apache/lucene/analysis/path/ReversePathHierarchyTokenizer.html[ReversePathHierarchyTokenizer], + which is suitable for domain–like hierarchies. Defaults to `false`. `skip`:: The number of initial tokens to skip. Defaults to `0`.