Expand description
Ingestion entrypoints and implementations.
Most callers should use ingest_from_path (from unified) which:
- auto-detects format by file extension (or you can override via
IngestionOptions) - performs ingestion into an in-memory
crate::types::DataSet - optionally reports success/failure/alerts to an
IngestionObserver
For ergonomic configuration, prefer IngestionOptionsBuilder over constructing
IngestionOptions directly.
Format-specific functions are also available under:
Re-exports§
pub use builder::IngestionOptionsBuilder;pub use observability::CompositeObserver;pub use observability::FileObserver;pub use observability::IngestionContext;pub use observability::IngestionObserver;pub use observability::IngestionSeverity;pub use observability::IngestionStats;pub use observability::StdErrObserver;pub use unified::ExcelSheetSelection;pub use unified::IngestionFormat;pub use unified::IngestionOptions;pub use unified::IngestionRequest;pub use unified::infer_schema_from_path;pub use unified::ingest_from_path;pub use unified::ingest_from_path_infer;pub use db::ingest_from_db;pub use db::ingest_from_db_infer;