Analysis on INFINI Pizza

Analyze text

Mon, 01 Jan 0001 00:00:00 +0000

Analyze text #

The analysis workbench: run the server’s tokenizers, normalizers, token filters and analyzers over sample text and see the exact token stream — the same components the indexing path uses, so what you debug here is exactly what collections run.

List components #

GET /_analysis/components

Returns every registered tokenizer, normalizer, token filter and named analyzer (the set a schema may reference — see custom analyzers for defining per-collection ones). The server ships 83 analyzers, 50 tokenizers, 15 normalizers and 327 token filters out of the box — the full catalog is on the built-in components page:

Built-in analysis components

Mon, 01 Jan 0001 00:00:00 +0000

Built-in analysis components #

The server ships 83 analyzers, 50 tokenizers, 15 normalizers and 327 token filters, registered at startup. The authoritative, always-current list on YOUR node is:

GET /_analysis/components

Components are referenced by name — in a field’s schema ("analyzer": "english"), in a custom analyzer definition, or in an ad-hoc _analysis/analyze pipeline.

Analyzers #

General purpose:

fingerprint, keyword, pattern, simple, standard, stop, whitespace

CJK and transliteration:

cjk, ik_max_word, ik_smart, jieba, kuromoji, nori, pinyin, smartcn stconvert_s2t, stconvert_t2s