etl_core/lib.rs
1//! The engine of the `etl-rs` framework.
2//!
3//! `etl-core` contains the pipeline runtime and every technology-neutral
4//! abstraction: records and their checkpoint tokens, the operator chain,
5//! the source and sink traits, checkpointing, backpressure, configuration
6//! loading, metrics, and the admin server.
7//!
8//! Applications should depend on the [`etl`](https://crates.io/crates/etl)
9//! facade crate rather than on `etl-core` directly.
10//!
11//! The architecture and its invariants are documented in `docs/DESIGN.md`;
12//! the metric taxonomy in `docs/METRICS.md`.
13
14// tokio's own sources change shape under `--cfg loom` (net disappears), so
15// anything touching tokio::net is compiled out of loom model builds.
16#[cfg(not(loom))]
17pub mod admin;
18/// Re-export of the [`bytes`] crate: [`RowEncoder`](sink::RowEncoder)
19/// signatures take [`bytes::BytesMut`], so connector authors can use this
20/// re-export instead of declaring their own `bytes` dependency (declaring
21/// one is also fine — versions are compatible per the workspace pin).
22pub use bytes;
23
24pub mod backpressure;
25pub mod checkpoint;
26pub mod config;
27pub mod deser;
28pub mod error;
29pub mod metrics;
30#[cfg(not(loom))]
31pub mod ops;
32#[cfg(not(loom))]
33pub mod pipeline;
34pub mod record;
35#[cfg(not(loom))]
36pub mod sink;
37#[cfg(not(loom))]
38pub mod source;
39pub mod telemetry;
40
41pub use error::{DeserError, ErrorClass, ErrorPolicy, FatalError, SinkError, SourceError};
42pub use record::{Flow, PartitionId, RawPayload, Record, RecordMeta};