Skip to main content
Version: 0.2.1

Tools and processors reference

This page is the single entry point for everything Lucenia can do to your data: the ingest processors that run while documents are written and the search processors that run while queries are served.

note

The word tool means two different things in these docs. The Ingestion tools and utilities section covers third-party data shippers (Beats, Logstash, Fluentd, OpenTelemetry), the Lucenia CLI, and migration tooling — programs that run outside the cluster. This page covers the tools and processors that ship inside the cluster.

Ask the cluster, not the docs​

A running cluster is always the authoritative inventory for the version you are on.

SurfaceRequestNotes
Ingest processorsGET /_nodes/ingest?filter_path=nodes.*.ingest.processorsComplete. Includes processors contributed by every installed module.
Search processorsGET /_nodes/search_pipelinesIncomplete — see the warning below.
warning

GET /_nodes/search_pipelines reports only request_processors and response_processors. It omits search phase results processors, which is where normalization-processor lives — the processor that makes hybrid search work. Do not treat its output as the full search processor list. The complete list is in Search processors.

Ingest processors​

Ingest processors transform documents on the write path, inside an ingest pipeline. The complete table, with a link to each processor's own page, is in Ingest processors.

The processors below have dedicated pages in this version:

ProcessorWhat it does
ellipseConverts an ellipse geometry (WKT or GeoJSON) into a polygon approximation and indexes it as a geo_shape or shape. Useful for directional or asymmetric coverage areas such as cellular sectors.

Search processors​

Search processors transform requests, responses, and intermediate phase results on the read path, inside a search pipeline. The complete tables are in Search processors.

They run in three places:

  • Request processors rewrite the query before it is executed — for example oversample, filter_query.
  • Response processors transform the hits that come back — for example collapse, truncate_hits.
  • Phase results processors run between search phases on the coordinating node. This is where normalization-processor lives, and it is the category GET /_nodes/search_pipelines does not report.