This page defines central terms in the Tenzir ecosystem.
The app is a web application that partially runs in the user's browser. It is written in Svelte.
Maintains partition ownership and metadata.
The catalog is a component in the node that owns the partitions, keeps metadata about them, and maintains a set of sparse secondary indexes to identify relevant partitions for a given query. It offers a transactional interface for adding and removing partitions.
Manages chunks of raw bytes by interacting with a resource.
- See all available connectors
Translates between bytes and events.
- See all available formats
Optional data structures for accelerating historical queries.
Tenzir has sparse indexes. Sparse indexes live in memory and point to partitions.
A host for pipelines and storage reachable over the network.
tenzir-node binary starts a node in a dedicated server process that
listens on TCP port 5158.
- Deploy a node
- Use the app to manage a node
- Use the REST API to manage a node
- Import into a node
- Export from a node
Runtime statistics about pipeline execution.
The building block of a pipeline.
- See all available operators
The horizontal scaling unit of the storage attached to a node.
- Control the partition size
- Configure catalog and partition indexes
- Select the store format
- Adjust the store compression
- Rebuild partitions
Combines a set of operators into a dataflow graph.
A named record type describing the top-level structure of a data frame.
An operator consuming input, without producing any output.
- See all available sinks
An operator producing output, without consuming any input.
- See all available sources
An acronym for Tenzir Query Language.
TQL is the language in which users write pipelines.
- Learn more about the language
An operator consuming both input and producing output.
- See all transformations