Mindbreeze GmbH, A-4020 Linz, 2024.
All rights reserved. All hardware and software names used are trade names and/or brands of the respective manufacturers.
These documents are strictly confidential. The transmission and presentation of these documents alone does not establish any rights to our software, our services and service results or any other protected rights. The passing on, publication or duplication is not permitted.
For reasons of easier readability, gender-specific differentiation, e.g. user, is not used. Corresponding terms apply to both sexes in the sense of equal treatment.
This document deals with the CJK Tokenizer Plugin. It allows Mindbreeze InSpire to crawl and understand Chinese or Japanese content. For example, sentences can be divided into individual parts (tokens) that belong together in order to provide an optimized search experience. The Tokenizer Plugin supports multiple Tokenizers. An external tokenizer service is also supported (not included).
If an external Tokenizer service is to be used, this service must already be configured.
To activate the CJK Tokenizer the following steps have to be performed:
The CJK Tokenizer plugin is configured as a single Launched Service. This is the only way to achieve high performance. After configuration, this Launched Service is referenced as a Postfilter and QueryTransformationService.
To set up the CJK Tokenizer Plugin Launched Service, switch to the "Index" tab in the configuration and add a new service in the "Services" section.
A free TCP port on the appliance on which it runs Launched Service.
Selects the Tokenizer mode. The following modes are selectable:
Character used to separate the tokens. The default value is \uFEFF . This value can also be changed for testing purposes. For the search to work correctly, however, the default value must be retained.
Tokenize ISO-8859-1 Text
If this option is activated, ISO-8859-1 encoded text is also processed by the tokenizer.
Enable Text Normalization
Excluded Properties Pattern
The properties configured here using regular expression are not processed by the tokenizer.
Note: only relevant if the value Jieba is selected at Tokenizer.
The dictionary used for tokenizing:
Depending on whether the service is used as a QueryExprTransformation service or as a post-filter, different settings can be used. However, the default value "Index" is sufficient for both service types.
Note: only relevant if the value HANLP is selected at Tokenizer.
[Deprecated] EndPoint URL
URL of the /parse servlet of the Tokenizer service
Note: only relevant if the value Kuromoji is selected at Tokenizer.
The postfilter is used by the tokenizer to tokenize (decompose) the contents at crawling time before they are stored in the index.
With the Tokenizer, the Transformation Service query ensures that the text entered by the end user in the search field is tokenized before the query. If this is not the case, the tokenization of the index does not match that of the search query. This would have the same effect as if you had not configured a Tokeinzer.
If documents already exist in your index, they must be re-indexed because the existing documents have not yet been tokenized.
The CJK Tokenizer Plugins runs a test servlet on the BindPort, which can be used for diagnostic purposes. For example, you can "tokenize" any text fragments in the web browser.
For example, the call results in:
<font color="#ffff00">-=清洁=- sync:ßÇÈâÈâ
Note: The default separation character is not visible. To make these separators visible, you can copy the result to an editor.