Documentation
How Bergman measures table health, resolves policy, plans maintenance, and decides — eight checks deep — whether a file may be deleted.
Bergman keeps Apache Iceberg tables healthy without a JVM: one crate, one binary, and a library any Rust service can embed.
Start with Getting started — the first command reads your catalog and changes nothing. To judge fit, read Status: what executes and what is refused. Before enabling deletion, read Orphan files, the safety model.
Start here
Configure
Operations
Snapshots
Expiring snapshots, what upstream decides, and reclaiming the files expiration leaves behind.
Orphan files
The one operation that can destroy a healthy table, and the eight independent checks standing in front of it.
Compaction
What triggers a rewrite, how file groups are bounded, how delete files are retired, and what Bergman refuses to rewrite.